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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so the safety profile is covered elsewhere. The only added value is the pointer that describe_operation supplies native request schemas, but return shape, pagination, and filtering behavior are entirely undisclosed.

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 first sentence is repeated twice word-for-word, wasting the most valuable position. The only substantive sentence is the trailing note about describe_operation, which should have been 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 no output schema, a fully undocumented nested query object, and a large family of similarly named template endpoints, an agent needs at minimum what the endpoint lists and what the query object accepts. Neither is provided; the description only points elsewhere for schemas.

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 (query, params) are opaque objects with additionalProperties and no properties documented. The description does not compensate at all; it only redirects the agent to describe_operation for the request schema, which is a hint rather than parameter semantics.

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 just the HTTP verb and path ("GET /api/templates/documents") duplicated verbatim, which restates the tool name and title rather than explaining what the tool returns. It does imply a read/list of document templates, but nothing distinguishes it from siblings like get_templates_documents_by_id, get_templates_contracts, or get_templates_leases.

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 given. The presence of get_templates_documents_by_id and related template endpoints means an agent must guess which list endpoint applies; the description offers no routing help.

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