marketing_attribution_export_async_status

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

Annotations already indicate readOnly, idempotent, non-destructive. The description adds a noteworthy behavioral detail about the shared path and provides a direct spec link, enhancing transparency 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 concise sentences with a useful link. No unnecessary words; front-loaded with purpose.

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?

Provides purpose, behavioral nuance, and a reference, but does not describe the return value or indicate what the status response looks like. Since there is no output schema, the agent lacks this information.

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 schema has one required parameter ('exportId') with 0% schema description coverage. The description does not explain this parameter's meaning or format; it relies on the parameter name. Some additional context would be helpful.

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 'Poll status of an async marketing-attribution export job,' specifying the verb 'poll' and the resource 'status.' This distinguishes it from related tools like 'start' and 'download' for the same export type.

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 use after starting an export by saying 'poll status,' but does not explicitly state when to use this tool versus other async status tools (e.g., for licenses or transactions). No exclusion criteria or alternatives given.

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