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

With no annotations, the description carries the full burden, and it does disclose two genuinely useful traits: the return is base64-encoded (large payload) and includes a sha256 for integrity checking, plus the strong hint that the artifact is an immutable snapshot ('byte for byte as it was made'). It omits error behavior (not-found, not-yet-generated), size limits, and whether retrieval is authorized per shop.

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 that puts the resource first and the delivery format second, with zero filler. Nothing could be removed without losing information.

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 one-parameter read with no output schema, the description usefully explains what comes back in the response body, which is the hardest part to infer. It is nonetheless incomplete on how to obtain the document_id and on failure modes, leaving real gaps for an agent invoking it cold.

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 0% — the single UUID parameter document_id is documented nowhere. The description never references it, so the agent must guess that the id comes from documents_list or a job record rather than, say, a job id.

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 names the resource precisely — a single stored job PDF — and adds distinguishing content (base64 payload, sha256, byte-for-byte fidelity), which separates it from a list tool. It never explicitly says 'retrieve by id' nor names the sibling (documents_list / media_get) it contrasts with, so identification works but requires inference from the schema.

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 statement of when to call this versus documents_list, media_get, or the other document siblings — no prerequisites, no mention of what happens if the PDF was never generated. Usage is only implied by the word 'One'.

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