The operation summary for an API is the first chance you have to describe the purpose of a single API operation in as few words as possible–don’t waste words, make them all count. Make your summaries reflect the verbs and nouns expressed via the path and HTTP method, making for an easy to understand summary of the operation being applied.
Make sure your API summaries are consistent across your API operations and paths. Publish just a bulleted list of all API operation summaries and read them aloud. Do they make sense? The sum of your API responses should add up the overall narrative of what an API can do, and work with the naming, tagging, and other metadata provided. Do the work to properly summarize the value provided by each API in the context of what your consumers need, not what you developed.