Get ad groups with core metrics

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

No annotations are provided, so the description carries the full burden. 'List' signals a read-only operation, and it discloses return content (status and metrics). However, it omits details like pagination behavior, default limit, or required permissions, leaving some behavioral uncertainty.

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 a single, front-loaded sentence that efficiently conveys the action, scope, and return contents without unnecessary words or repetition.

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 limited parameter descriptions, the description provides a basic understanding of the tool's purpose and output but lacks details about limit defaults, status filtering, and response shape. It is adequate for selection but not fully complete.

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 only 33%: only campaignId has a description. The description adds context for campaignId ('optionally filtered to one campaign') but does not explain the limit parameter's effect or the status parameter's filtering role, leaving two of three parameters underdocumented.

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 uses the specific verb 'List' with the explicit resource 'ad groups' and adds scope ('optionally filtered to one campaign') plus return content ('status and core performance metrics'). This clearly differentiates it from sibling tools like get_campaigns and get_keywords.

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 this tool is for listing ad groups with optional filtering by campaign, but it does not explicitly state when to prefer it over alternatives like search_gaql or get_campaigns. No exclusions or alternative-recommendation language is present.

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