Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false. The description adds valuable domain context that reports are represented by docs in the API and that the underlying call is GET /docs/. It repeats 'read-only' but does not cover pagination or auth behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, front-loaded with the action and endpoint mapping, with zero wasted text. The limitation note follows immediately.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 10-param list tool with no output schema, the description gives adequate purpose and a key domain mapping, while annotations cover safety. However, it omits pagination, filtering, and authentication guidance that an agent would need to call it confidently.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 10 parameters and only 70% schema description coverage, the description adds no parameter meaning at all. It does not explain page, filter, page_size, account_id, auth tokens, or the undocumented id and include_doc_type fields.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: 'Lists saved/shared reports using GET /docs/.' Adds the useful API mapping that reports are represented by docs. Does not explicitly differentiate from siblings like get_report or delete_report, but the listing scope is clear.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides no when-to-use guidance, no alternatives, and no exclusions beyond the read-only limitation. An agent gets no help deciding between list_reports and get_report or other list endpoints.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.