get_ad_detail_report

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

No annotations provided. The description does not disclose side effects (none expected for a report), rate limits, authentication needs, or data freshness. The 'get' verb implies read-only but is not explicitly stated.

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?

Description uses clean docstring format with a concise purpose sentence followed by parameter descriptions. No extraneous text, though it could be slightly shorter. No return value description, which is a minor omission.

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 no output schema and five parameters, the description lacks return value structure, pagination behavior, and error handling details. For a report tool, describing the response is essential. Behavioral gaps also remain.

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 0%, but the description adequately explains all five parameters: advertiser_id, start_date/end_date (with format hint), page (default), page_size (default and max). Adds meaning beyond the schema.

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 retrieves an ad-level detail report with specific performance metrics (impressions, clicks, cost, conversions). The tool name is descriptive and distinct from siblings like get_ad_detail (single ad) and other report tools.

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?

No guidance on when to use this tool versus alternatives like get_campaign_report or get_creative_report. No mention of prerequisites, context, or exclusions.

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