Often, components that do less are more powerful. REST has six operations, SQL four and MQ two. LISP uses only nine words to define the whole of computing. Most would agree that additional features and responsibilities in these applications would be detrimental. Developers should use the same care to avoid overloading a class with more than one responsibility.
OO is all about responsibility assignment:
Responsibilities are not the sort described by "allow the user to enter and save customer information" (that's the use case) but are discrete, divided among the application layers (presentation, domain and persistence) and assigned at the component level.