Bob Martin raises a good example in InformIT: Robert C. Martin’s Clean Code Tip of the Week #1: An Accidental Doppelgänger in Ruby > Duplication of two functions that do the same thing but mean different things by it.
I recently stumbled into a slightly different take on the question of should a function say what it does or what it intends?
When a function implements business process Alpha that today consists of steps A and B (but tomorrow may change) should you call the function
DoBusinessProcessAlpha or call it
One answer would be, if the function is in a public package which exposes business functionality then the name should probably show that it does
BusinessProcessAlpha. But if it is a private, not exposed, function then the reader is probably looking for the detail, that it does
The question is more awkward if Steps A and B are themselves business process functions. That is, if you asked your customer, they would understand what steps A and B mean.
I suppose in that case you could always call it