The description for each individual API operation should be one or two paragraphs that articulate what is happening when you request the operation, leaving the other parameters, request bodies, responses, examples, and other details to other parts of the OpenAPI specification. Use the description property to share a simple narrative about what each API consumer expect when requesting the operation, keeping consistent across API operations.
Establish the max number of characters that operation summaries should be and then automate this across teams, pushing teams to request exceptions if they need to go higher–it is a great way to gather feedback on policies from teams producing APIs. Encourage teams to use AI when writing descriptions if they find it challenging to write the words themselves. However it gets done there should be simple, useful, short descriptions of what each individual API operation actually does.