get_account_export

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

Annotations indicate readOnlyHint=true, so the tool is read-only. The description adds behavioral context about polling and the need to wait for status 'finished' to obtain the download URL. This extra detail goes beyond annotations. However, it does not mention idempotency or rate limits, which are minor omissions.

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 concise, with a clear first sentence stating purpose, followed by usage instructions, and a structured Args and Returns section. Every sentence adds value without redundancy.

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?

The description covers the use case, how to obtain the export_id, and what the return looks like (JSON fields). It also mentions the output schema implicitly. The only gap is the missing explanation of the 'account' parameter, which slightly reduces completeness.

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?

The description explains the required export_id parameter and how to obtain it, but fails to mention the optional 'account' parameter. Since schema description coverage is 0%, the description should cover both parameters. This omission leaves the agent without guidance on the account parameter, reducing semantic clarity.

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 retrieves status and download URL for a single account export job, using a specific verb and resource. It distinguishes itself from sibling tool list_account_exports by explicitly stating that list_account_exports is for browsing and discovering IDs, thus preventing confusion.

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 provides explicit instructions: 'Use to poll an export until its status is finished and then read its download_url. Use list_account_exports to browse all exports and discover IDs instead.' This clearly tells when to use this tool and when to use the sibling, offering strong usage guidance.

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