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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered elsewhere. The description adds no behavioral context of its own: no pagination, no result size, no auth or scope notes, and no statement of what the returned document list contains.

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 duplicated verbatim, which is pure waste, and the remaining text is an operation ID plus a boilerplate pointer. There is no front-loaded statement of intent, so the size is small but poorly structured rather than concise.

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 read endpoint with a nested 'query' object, no output schema, and 0% parameter documentation, the description should explain at minimum what the document list represents and how to page/filter it. It leaves those gaps open, so an agent could invoke it but not predict or shape the result.

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 description compensates only by mirroring the ':id' path segment, without explaining that it maps to params.id or what constraints apply. The free-form 'query' object is entirely unexplained, leaving half the parameters undocumented in both places.

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 repeats the raw endpoint 'GET /api/sites/:id/documents' twice, which only restates the name/title. It signals a read of documents scoped to a site id, but never says what these documents are (files, contract docs, generated artifacts) or how they relate to sibling tools like get_contracts_by_id_documents.

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?

The only guidance is a pointer that 'describe_operation provides native request schemas', which is a note about schema discovery, not about when to choose this tool over alternatives. No conditions, prerequisites, or sibling routing are given.

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