list_account_exports

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

Beyond annotations (readOnlyHint=true), description adds 'Max 10 concurrent requests' and 'Authenticated via API key' – useful behavioral constraints not in annotations. Consistent with read-only nature.

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?

Well-structured with clear sections: purpose, usage, behavioral notes, parameters, returns. Slightly verbose with repeated authentication info, but overall efficient for the information conveyed.

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?

Covers all necessary aspects: purpose, when to use, behavioral constraints, parameter explanation, and detailed return format including field names. Adequate for a simple read-only list tool with one optional parameter.

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?

Though input schema lacks description, the tool's description includes an 'Args' section explaining the account parameter in detail, including how to use different accounts and reference to list_accounts. This fully compensates for 0% schema coverage.

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?

Description clearly states 'List account export jobs' with specific resource and verb. Distinguishes from sibling get_account_export by noting it provides the full record and download URL. No ambiguity.

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 says 'Use this to track export requests and discover export IDs and their status' and recommends get_account_export for full details. Mentions concurrency limit and read-only retry safety. Could be improved by contrasting with other list tools, but provides clear context.

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