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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false and destructiveHint=false, so safety is covered. The description adds nothing beyond that — no mention of pagination, filtering behavior, or response shape for a list endpoint, so it does not earn credit for extra context.

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?

It is short, but the first sentence is duplicated verbatim, wasting half the text. The one useful clause (describe_operation provides native request schemas) is buried after a redundant repetition and an opaque operation ID.

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?

With no output schema, 0% parameter coverage, nested objects, and a huge sibling set of recon-docs tools, the description should explain inputs and what is returned. Instead it points at describe_operation and leaves every substantive question unanswered.

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?

Schema description coverage is 0% for the two parameters: 'query' is an unconstrained free-form object and 'params' is an empty closed object, with no explanation of what they accept. The description does not compensate; the sole hint is to call describe_operation for the native schema.

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?

The description only restates the HTTP path 'GET /api/recon-docs/statements', which is essentially the tool name/title repeated. It never says in plain language what a 'statement' is here or how this list endpoint differs from the sibling get_recon_docs_statements_by_id.

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?

There is no when/when-not guidance and no routing to alternatives such as get_recon_docs_statements_by_id_aeb76d55db876da12d8696b9. The only actionable hint is that describe_operation supplies native request schemas, which is a schema-lookup pointer rather than usage guidance.

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