Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnly, idempotent, non-destructive, open-world. The description adds real value beyond them by explaining the response fields that carry non-obvious meaning: MCP endpoint URL, mcpVerified (probe success), and mcpAuthRequired when the endpoint returned 401/403. This tells the agent how to interpret ambiguous results, which annotations cannot. It omits pagination/ordering edge cases, so not a 5.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.