list_exports

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

Discloses output format, status values (with case sensitivity), rate limit (1 per minute), and that downloadLink populates only when finished. Annotations already declare readOnlyHint=true, consistent with read behavior.

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?

Two sentences with full purpose, output spec, usage instruction, and rate limit. Front-loaded: first sentence gives purpose, second details output and usage.

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?

Output schema exists (not shown but indicated true), and description fully covers the response fields and status semantics. Complete for a list/poll tool.

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 100% with a description for the single parameter, so baseline is 3. Description adds no extra parameter info beyond the schema.

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?

Clearly states 'List requested CSV export reports and their processing status,' with specific verb and resource. Differentiates from siblings by focusing on CSV exports and polling workflow.

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?

Explicitly instructs to poll after request_export until status is 'Finished' and provides polling guidance. No explicit when-not or alternatives, but the context is clear.

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