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

Annotations cover the safety profile (read-only, idempotent), but the description adds substantial behavior the annotations cannot: newest-first ordering, pagination, the fact that download_url only works in a signed-in browser session, and the constraint that anonymous links must be fetched individually elsewhere. This is real operational context beyond structured fields.

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?

Front-loaded with purpose and filters, then return fields, then the signed-URL caveat — a logical order with no filler sentences. It is fairly dense, but every clause carries information an agent needs.

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?

With no output schema, the description enumerates the returned fields (id, export_type, status, name, filters, created_at, completed_at, download_url, download_expires_at) and their conditional availability, and covers pagination and the download-link caveat. Nothing needed to call or interpret it is missing.

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 100%, so the schema already documents page, page_size, status and export_type. The description restates the two filterable fields and inlines the status values, which adds marginal reinforcement but no syntax or format detail beyond the schema. Baseline 3 applies.

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?

States a specific verb and resource ('List the authenticated customer's recent exports'), plus ordering ('newest first') and scope ('the authenticated customer's'). It explicitly distinguishes itself from the sibling get_export for the signed-URL case.

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?

Names the alternative (get_export with include_signed_url) and the precise condition that selects it ('only when the user asked for one'), and states that login-free links are never returned here. Both the when and the when-not are explicit.

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