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

Annotations declare readOnlyHint=false, yet the description frames the operation as pure retrieval ('Return the PDF record'), which would lead an agent to treat it as a safe read with no side effects. This is the same class of mismatch as a write tool advertised as read-only, so it is flagged as an annotation contradiction; the description also says nothing about permissions, rate limits, or whether an export artifact is created or logged.

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 filler — the verb, resource, scope and output format all arrive immediately. Its brevity is legitimate rather than padding, though the same compression is what leaves the parameters and usage conditions unexplained.

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 two-parameter tool with zero schema description coverage, no output schema, and a misleading read-only framing, the description covers only the return medium ('embedded document') and leaves the identifier semantics, preconditions, and side-effect profile unaddressed.

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% for two parameters, and the description does not identify either one: it never says what 'id' refers to, that 'decisionId' exists or is optional, or which identifier to supply for a given approval. It gestures at identifying an approval but provides no compensating semantics for the undocumented inputs.

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?

Names a specific verb (Return/Export), a specific resource (the PDF record) and its scope (a completed customer approval), plus the delivery format (embedded document). An agent can tell it apart from plain data getters like get_approval or get_decision, though it never explicitly contrasts itself with those siblings.

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 phrase 'a completed customer approval' implicitly restricts this to finished approvals and hints at a precondition, but there is no explicit when-to-use guidance, no statement of when to prefer it over get_approval/get_decision, and no note about whether incomplete or pending approvals are accepted.

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