Run a saved report

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

With no annotations provided, the description does the heavy lifting: it discloses that reporting is asynchronous, that this call waits for completion, and that the operation is read-only and never mutates the report definition. It stops short of disclosing rate limits, timeout behavior, or how results are truncated.

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?

Four short sentences, front-loaded with purpose and followed by the resource-name source, async behavior, and safety note. Slightly more than strictly necessary, but each sentence adds usable information.

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?

No output schema exists, and the description compensates by stating that rows are returned and that the call blocks until the async job finishes. It does not describe row shape or result-size behavior beyond the schema's maxRows, but is sufficient for correct invocation.

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 description coverage is 100%, so both parameters are already documented, and the description merely repeats the reportName example format. The maxRows cap (1-5000, default 500) is left entirely to the schema. Baseline 3 is appropriate when structured data carries the semantics.

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?

States a specific verb and resource ('Run a saved Ad Manager report and return its rows') and differentiates itself from the list_* siblings by making clear it executes an existing definition rather than enumerating resources. An agent can tell this apart from list_reports without opening either schema.

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 routes the agent to list_reports as the source of the required reportName, which is the key precondition. It does not state when not to use it or what to do on failure/timeouts, but the practical entry condition is covered.

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