google_ads_ad_groups_list

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

The description declares the tool as read-only, which is the key behavioral trait. No annotations are present, so the description adequately handles transparency. It could mention pagination or rate limits, but for a simple list tool this is sufficient.

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 with three sentences: first states the action and options, second lists return fields, third provides usage context. No redundant information, and front-loaded with key details.

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?

For a simple list tool with three optional parameters and no output schema, the description covers purpose, usage context, and return fields. It could include information on result limits or ordering, but it is complete enough for correct tool 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?

Schema coverage is 100%, so baseline is 3. The description adds value by explaining that customer_id falls back to environment variables and that omitting campaign_id lists across the entire account, which complements the schema definitions.

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 lists ad groups in a Google Ads account, with optional scoping to a parent campaign and filtering by status. It lists the return fields (id, name, campaign_id, status, type, cpc_bid_micros, ad_rotation_mode) and distinguishes itself from sibling tools like ad_groups.create/update and 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?

The description explicitly states when to use this tool: to locate an ad_group_id before calling ad_groups.create/update or ads.create. It also advises using ads.list filtered by ad_group_id if the ID is already known, providing clear alternative usage guidance.

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