create_async_report

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

With no annotations provided, the description carries the full burden. It conveys the async nature and the need to poll, but does not disclose auth requirements, rate limits, or whether it is destructive (likely not). This is adequate but not comprehensive.

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 short, front-loaded sentences with no extraneous information. Every word earns its place.

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 covers the purpose and return value, and references the polling sibling. Given 7 well-described parameters and no output schema, it is fairly complete. Minor gap: lacks mention of any constraints or limits.

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 baseline is 3. The description itself does not add any additional parameter semantics beyond what the schema already provides. The schema descriptions are good, so no deduction.

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 it creates an async insight report for large data queries, and specifies it returns a report_run_id for polling via get_async_report. This distinguishes it from other sibling tools that may be synchronous or for other purposes.

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 indicates the tool is for large data queries, implying it is for heavy workloads. It explicitly mentions polling with get_async_report, providing a clear usage flow. However, it does not explicitly contrast with synchronous insight tools like get_ad_insights, leaving some ambiguity about when to use this vs. those.

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