google_ads_get_audience_performance

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

No annotations are provided, so the description carries the full burden. It states 'Get performance metrics' (a read operation) and describes the return type as a breakdown by audience. This is adequate but doesn't discuss rate limits, data freshness, or other behavioral traits.

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 structured with a brief intro, parameter descriptions, expected return, and a complete example. It is concise with no wasted words and front-loaded with purpose.

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 the tool has an output schema (context signal: has output schema: true), the description appropriately omits return format details. It covers purpose, all three parameters, and provides an example. This is sufficient for an agent to understand and invoke the 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 0%, so the description adds value by specifying customer_id format ('without hyphens'), campaign_id as optional filter, and example date ranges (TODAY, LAST_7_DAYS, etc.). However, it doesn't list all possible date_range values or clarify campaign_id format further.

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 the verb and resource: 'Get performance metrics by audience.' It specifies what it does (see which audiences drive best results in terms of clicks, conversions, ROI). This distinguishes it from sibling tools like account_performance or campaign_performance.

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 implies usage for audience-level performance analysis but does not explicitly state when to use versus alternatives like google_ads_search_google_audiences (which lists audiences) or other performance tools. No exclusions or prerequisites are mentioned.

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