google_ads_ad_groups_list

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

The description states 'read-only' and lists return fields, but no annotations are provided. It does not mention pagination or rate limits, but for a list operation this is adequate and transparent.

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?

Two sentences, front-loaded with purpose, no wasted words. Efficient and clear.

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 3 parameters all documented in schema, and description adds usage and behavior context, it is complete. Output schema not needed for list 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 100%, baseline 3. The description adds context: 'optionally scoped to a single parent campaign' and 'filtered by status', plus explains customer_id fallback, adding value beyond 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 'Lists ad groups in a Google Ads account' and specifies optional scoping to a parent campaign and filtering by status, with a list of returned fields. This is specific and distinguishes from sibling tools like campaigns_list or ads_list.

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?

Explicit guidance: 'Use this to locate an ad_group_id before calling ad_groups.create / update or ads.create; if you already have the id, fetch it directly via ads.list filtered by ad_group_id.' Also explains fallback for customer_id from credentials.

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