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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is fully covered by structured data. The description adds nothing beyond that — no mention of pagination, filtering behavior, or the shape of returned statement templates. It does not contradict the annotations.

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?

The text is short but wastes its opening sentence by duplicating the endpoint path verbatim, then repeats the same phrase a second time. The one informative element (the describe_operation pointer) is buried at the end rather than front-loaded.

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 0% schema coverage, a nested free-form query object, and no output schema, the description carries the full burden of explaining inputs and behavior but supplies essentially none. An agent knows only that it is a read on a statement-template endpoint and must fall back to describe_operation for anything usable.

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% and the two parameters are opaque: 'query' is a free-form object with additionalProperties and 'params' has no defined properties. The description provides no information about what query keys are accepted or what these parameters do, leaving an agent unable to construct a meaningful call.

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 is a verbatim restatement of the endpoint path, which itself just echoes the title. An agent can infer 'read statement templates for recon docs' from the URL segments, but no plain-language statement of what a statement template is or contains is offered, and there is no differentiation from sibling template tools such as get_recon_docs_templates_audit_package.

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?

No when-to-use, when-not-to-use, or alternative guidance is present. The only directive is a pointer that describe_operation provides native request schemas, which is a useful routing hint but does not tell the agent when this tool is the right choice over the many other recon-docs and template getters.

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