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

Annotations already mark readOnlyHint: true, covering safety. The description adds behavioral context by stating it returns a 'fresh download URL' (implying time-limited or regenerated) and 'linked insights' (additional data), which are not obvious from the schema. This goes beyond the read-only annotation without contradicting it.

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?

A single, front-loaded sentence with no fluff. Every word adds value: 'specific' scopes it, 'fresh download URL' and 'linked insights' describe key outputs. Ideal conciseness.

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 simple single-parameter read operation with annotations and no output schema, the description provides sufficient detail on what the response contains. It could elaborate on what 'linked insights' entails, but overall it's complete enough for an agent to invoke correctly.

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 coverage is 100% with document_id already described as coming from listDocuments. The description does not add any parameter-specific meaning beyond echoing the need for a specific document. Baseline 3 is appropriate as the schema fully documents the parameter.

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?

Description clearly states the tool retrieves a specific document by ID, and highlights two distinctive outputs (fresh download URL and linked insights) that separate it from listDocuments and other siblings. The verb 'Get' and resource 'specific document' are explicit and unambiguous.

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 description implies use when a specific document's details are needed, especially to obtain a fresh URL or insights. It does not explicitly mention when not to use or name alternatives, but the context (sibling listDocuments) provides implicit differentiation. Clear enough but lacks exclusionary guidance.

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