There is a factor that affects the choice of button's label - application's posture.
According to A. Cooper "About Face 3. The Essentials of Interaction Design":
... applications fit into four categories of posture: sovereign,
transient, and daemonic...Programs that monopolize users’ attention
for long periods of time are sovereign posture applications.
He cited as examples of sovereign applications word processors, spreadsheets, and e-mail applications.
A product with a transient posture comes and goes, presenting a single
function with a constrained set of accompanying controls.The
application is invoked when needed, appears, performs its job, and
then quickly leaves, letting the user continue her normal activity,
usually with a sovereign application.
And now regarding button's labels:
Transient applications should have instructions built into their surface. The
user may only see the application once a month and will likely forget
the meanings and implications of the choices presented. Instead of a
button captioned Setup, it’s better to make the button large enough to
caption it “Set up user preferences.” The verb/object construction
results in a more easily comprehensible interface, and the results of
clicking the button are more predictable.
So, as you see, sometimes it's better to label a button with more clear and precise text but of course within a reasonable length. Using verb/object construction is enough. Don't put words that don't add any extra clarity.
Of course, there is an obvious principle - the button's label has to clearly explain what the button does. And the shortest way to label a button is to use the verb representing the action that performs after the button is pressed regardless of the application's posture. So, in common case, if the button performs two actions it must be labelled with two respective verbs. But I would say that there is an exception. If the second action is "exit" or "close" (like in your examples) there is a case when you don't need to say about it in the label. And this case is dialog box. Most of them have buttons like "save", "cancel", "OK", but not "save and close", "cancel and close", "OK and close". And we are all familiar with their behaviour and expect that most of the "main" buttons in a dialog box make respective action and close the dialog. I said "most of the main buttons" because here there is an exception too. I mean specific buttons like "apply" in Window's File Explorer Options dialog. But again, in common case, if it's a dialog's button you can use just "save", but if it's a button on main window use "save and close" or "save and exit" or else a user will be surprised and frustrated by the unexpected result.