List Google Ads Ad Groups

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

The description is consistent with the `readOnlyHint` and `destructiveHint: false` annotations, indicating a read operation. However, it adds no new behavioral details about auth, rate limits, or response streaming beyond what annotations already convey.

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 core functionality. It is concise without being overly terse, though it could briefly mention key parameters.

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 6 parameters and an output schema, the description is minimal. It does not explain pagination, field meanings, or result limits, but the output schema partially compensates. Completeness is adequate but not thorough.

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 only 50% schema description coverage, the description should compensate by explaining parameter intent, but it only restates the optional campaign filter without adding meaning to `status`, `page_size`, or `privacy_mode` 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 clearly states the action 'List ad groups' and distinguishes the scope: 'under a campaign (or all campaigns) in a customer.' This differentiates it from sibling tools like 'google_ads_list_campaigns' and 'google_ads_list_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 the tool is for listing ad groups but lacks explicit guidance on when to use it versus alternatives like 'google_ads_list_keywords' or 'google_ads_list_campaigns'. No 'when-not-to-use' or context cues are provided.

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