google_ads_list_ad_groups

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

No annotations are provided, so the description carries full burden. It only states it returns 'key metrics' without elaborating on behavior like pagination, rate limits, or data scope. Minimal behavioral context beyond the basic operation.

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 extremely concise, with a single sentence for purpose and a structured Args/Returns section. No redundant text, front-loaded with the action.

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 simplicity of the tool and the existence of an output schema, the description is mostly complete. It covers purpose, filters, and return type. Minor gaps: does not explicitly state that customer_id is required (though implied) and omits pagination info.

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?

The description adds value beyond the input schema by specifying customer_id format ('without hyphens') and enumerating allowed status values ('ENABLED, PAUSED'). Schema coverage is 0% but the description itself provides meaningful parameter details.

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 'List ad groups with optional filters', specifying the verb (list) and resource (ad groups). It distinguishes from sibling tools like google_ads_list_ads and google_ads_list_keywords by focusing on ad groups.

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 lists optional filters but does not explicitly guide when to use this tool versus alternatives like google_ads_get_ad_group_details for specific details or google_ads_list_ads for ads. Usage is implied but lacks exclusions or alternative suggestions.

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