retrieve_export

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

The description discloses the return format (Base64-encoded bytes) and implies a read operation by using 'retrieve'. However, with no annotations, it does not explicitly state non-destructive behavior, required permissions, or any side effects (e.g., whether multiple retrievals are possible).

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 deliver the purpose and output format directly with no extraneous words. Every sentence adds value.

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 explains the output format, which is helpful given no output schema. However, it lacks information about error handling (e.g., what if the export is not yet completed or the id is invalid) and does not address the dependency on export completion status.

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 single 'id' parameter is described as 'by id', but no additional meaning or format constraints are provided. While the context of 'export id' is inferred, schema coverage is 0%, so the description adds minimal value 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?

The description clearly states the action (retrieve), the resource (binary content of a completed export), and the input (by id). It also specifies the output format (Base64-encoded string under 'data' key). This distinguishes it from sibling tools like 'request_export_report' or 'get_export_status'.

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 the tool should be used after an export is completed, but does not explicitly state when to use it versus alternatives like 'get_export_status' or 'request_export_report'. No guidance on prerequisites or exclusions.

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