get_ad_group_report

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

No annotations provided, so description carries full burden. Describes read-only nature, grouping by country/region, grand totals, and default time range/granularity. However, does not cover potential error behaviors or rate limits.

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?

Three well-structured sentences, front-loaded with core purpose, no redundant information. Every sentence adds value.

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?

Despite no output schema, description lists the metrics returned. Covers key behavioral aspects and parameter defaults. Could include more on error handling or pagination, but adequate for a report tool.

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 100%, baseline 3. Description adds context beyond schema: e.g., 'Obtain from list_campaigns' for campaignId, defaults for startDate/endDate/granularity, and meaning of adGroupIds absence.

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 it fetches ad group performance metrics for a specific ASA campaign, listing specific metrics (impressions, taps, etc.). It distinguishes from siblings by naming get_campaign_report and get_keyword_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?

Explicitly says when to use this tool vs. alternatives ('Use get_campaign_report for a campaign-level summary, or get_keyword_report for keyword-level detail.'). Also mentions authentication requirements and defaults.

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