google_ads_ad_groups_list

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

Declares 'Read-only' which is critical since no annotations exist. Lists exact return fields (id, name, campaign_id, status, type, cpc_bid_micros, ad_rotation_mode). Does not mention pagination or auth fallback but sufficient for basic list 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?

Three sentences with clear front-loading: main action, scoping/filter options, return fields, and usage guidance. No filler.

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?

Complete for a simple list tool: explains purpose, usage, and return schema. Lacks pagination/result limit details but that's a minor gap given no output schema and simple optional filters.

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 has 100% coverage with descriptions for all three optional params, so description adds little beyond restating optional scoping and status filtering. Baseline 3 is appropriate; no meaningful new param context.

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?

Clearly states it lists ad groups with optional scoping/filtering. Differentiates from related tools by explicitly pointing to ads.list for direct fetch and create/update for needing an ID.

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?

Explicitly says when to use: to locate ad_group_id before create/update calls. Also says when not to: if you already have the id, fetch directly via ads.list filtered by ad_group_id.

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