google_ads_get_ad_performance

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

No annotations are present, so the description must fully disclose behavior. It only says 'Get ad performance metrics' and returns an 'Ad performance report', which is vague. It does not mention whether data is aggregated, what metrics are included, or any limitations like rate limits or data freshness.

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?

The description is concise with a clear one-sentence purpose and structured Args/Returns section. However, the Returns section is too vague ('Ad performance report') and could be more informative without adding much length.

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?

With 3 parameters, an output schema, and many sibling tools, the description is adequate but lacks details on what metrics are included, whether it returns per-ad data or summaries, and how it differs from similar tools. The output schema likely specifies the structure, but the description doesn't bridge that gap.

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 0%, so the description compensates by explaining parameters: customer_id format (without hyphens), ad_group_id as optional filter, and date_range with example values (TODAY, YESTERDAY, etc.). This adds meaningful context 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 states 'Get ad performance metrics' which is a clear verb+resource pair. However, it does not differentiate from sibling tools like google_ads_campaign_performance or google_ads_get_ad_group_performance, leaving ambiguity about what exactly 'ad performance' entails compared to other reporting 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 is provided on when to use this tool versus alternatives. Given many sibling performance reporting tools, the description should indicate when this is appropriate (e.g., for individual ad-level metrics) versus for campaigns or ad groups.

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