Create performance report (async)

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

Discloses async nature, immediate return, and typical 1-15 min completion (up to 3h). No contradiction with annotations (readOnlyHint=false, destructiveHint=false, openWorldHint=true).

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?

Single paragraph packed with info; could benefit from bulletization. Front-loads key async behavior and workflow.

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 purpose, workflow, timing, examples, and common ids. No output schema, but explains return of reportId and polling needed. Missing explicit detail on groupBy/columns beyond examples, but schema covers those.

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?

Schema coverage is 78%; description adds common reportTypeIds and example columns, plus hint to omit profileId for default. Adds value beyond schema descriptions.

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 the tool requests an async performance report for Sponsored Products, Brands, or Display, returning a reportId. It lists common reportTypeIds, distinguishing it from siblings like get_report_status and download_report.

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?

Provides explicit workflow: request with create_report, poll with get_report_status, fetch with download_report. Mentions typical completion times. However, no comparison to alternative report creation tools like dsp_create_report.

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