Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of behavioral disclosure. It states the action is to 'List patches', implying a read-only operation, but doesn't cover aspects like permissions needed, rate limits, output format, or error handling. This leaves significant gaps for a tool with behavioral implications.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.