Export Documents

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

Annotations set readOnlyHint=true, indicating no destructive side effects. The description adds context: it generates a packaged file (ZIP) and returns a download URL, consistent with read-only behavior. It explains the organization and filtering, which goes beyond annotations without contradiction.

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 two sentences, front-loading the main action and result. Every sentence adds value: what is generated, how it's organized, optional filters, and output type. No extraneous 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 simple read-only export tool with two optional parameters and no output schema, the description covers the core functionality: exported content (all documents), organization (by year and type), optional filters, and return format (temporary URL). It does not detail URL expiration or size limits, but these are minor gaps.

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%, so the description carries the burden. It explains that 'type' filters by document type (charges/mobilier/travaux as implied in the first sentence) and 'year' filters by year. This adds meaning beyond the bare schema, though it does not enumerate possible string values for type.

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 clearly states the tool generates a ZIP file containing all user supporting documents (invoices, receipts, quotes), organized by year and type. It specifies optional filtering and a temporary download URL. This clearly distinguishes it from sibling tools like attach_document or list_expenses.

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 usage for exporting documents with optional filters but does not provide explicit guidance on when to use this tool versus alternatives. No exclusions or when-not-to-use scenarios are mentioned.

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