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

Annotations already declare the operation read-only, non-destructive, and non-idempotent. The description adds that formats and current document permissions are enforced, which is useful behavioral context, but it does not explain the download result or failure behavior when permissions or formats are rejected.

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 description is a single dense sentence with the key action front-loaded and no filler. Every clause contributes supported document types, formats, or enforcement context.

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 low-complexity export tool whose annotations cover safety, the description covers supported outputs and permission enforcement. However, with no output schema it should say what the tool returns (file, URL, bytes, etc.), and it should clarify how document_id is obtained or used.

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%, so the description must compensate. It maps document categories to CSV, JSON, Excel, and original PDF/image ZIP outputs, adding meaning to the format enum, but it leaves document_id unexplained and does not fully specify which formats apply to which saved document types.

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 gives a specific verb (Download/export) and resource (saved document), and it enumerates the document types and output formats supported. It does not, however, distinguish this tool from nearby siblings such as export_saved_invoice or export_original_pdfs.

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?

Listing bank/table, rate-confirmation, import-VAT, and specialized original documents implies when the tool applies. But there is no explicit guidance on when to choose this over sibling export tools or when not to use it.

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