marketing_attribution_export_async_download

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

Annotations already indicate read-only, idempotent, and non-destructive behavior. The description adds valuable context: request timeout (10 min, overridable) and error scenario (404 if not done). This enriches beyond annotations.

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 plus a spec link. No wasted words; critical info (purpose, precondition, timeout, error) is front-loaded. The link provides optional detail.

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?

Given the single parameter and no output schema, the description covers essential behavior: what it does, when to use it, timeout, and error handling. It is nearly complete for a download tool, though output format details are minimal.

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?

Only one parameter (exportId) with 0% schema description coverage. The description implies it's the ID of the completed export but does not explicitly define the parameter format or source. Slightly below baseline due to coverage gap.

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 'Download a completed async marketing-attribution export' with a specific verb and resource, distinguishing it from related start and status tools. The return type 'JSON records' is also specified.

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 states to only call after the *_status endpoint reports DONE, otherwise a 404 error occurs. This provides clear when-to-use guidance and preconditions.

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