google_ads_get_ad_group_performance

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

No annotations are provided, so the description must solely convey behavioral traits. It only says 'Returns: Performance metrics' without specifying what metrics (e.g., impressions, clicks, cost) or side effects. The generic term 'performance metrics' lacks the detail needed for transparent execution.

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, front-loading the purpose, then clearly separating Args and Returns sections. It is easy to parse, though the Args section could be more structured (e.g., markdown bullet list). Overall efficient and well-organized.

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 existence of an output schema (not shown), description need not detail return values, but it fails to provide usage context among many siblings, behavioral notes, or parameter provenance (e.g., how to find ad_group_id). This leaves an AI agent underinformed for correct selection and invocation.

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?

With 0% schema description coverage, the description adds meaningful context: clarifies customer_id format ('without hyphens'), lists example date_range constants, and hints at parameters' roles. This significantly aids parameter understanding beyond the bare 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 the tool retrieves performance metrics for an ad group over a date range, specifying the resource 'ad group'. However, it does not distinguish itself from sibling tools like google_ads_get_ad_performance or google_ads_get_keyword_performance, missing an opportunity to clarify scope differences.

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 provides no guidance on when to use this tool over alternatives, when not to use it, or any prerequisites. It only states the basic operation, leaving an AI agent without context for selection among many similar siblings.

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