google_ads_ad_groups_update

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

No annotations provided, so description carries full burden. It discloses partial update behavior, return of updated ad group, mutability, reversibility via rollback_apply, and non-cascade to ads/keywords. No contradictions.

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, concise and front-loaded with key actions. Every sentence adds value, including reversible and scope limitations. No unnecessary information.

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 update tool with no output schema, description provides sufficient context: partial update, return value, reversibility, and scope boundaries. No missing critical information.

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. Description adds context about partial update but does not elaborate on individual parameters beyond what schema provides. Adequate but not above baseline.

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 verb (update), resource (ad group), and specifies it's a partial update. It also distinguishes from sibling tools by noting it does not cascade to ads or keywords, using explicit tool names for those.

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 states when to use this tool (partial update of ad group settings) and when not (for ads/keywords changes). Directs to alternatives like google_ads_ads_update and google_ads.keywords.*. Also clarifies that status-only changes are handled here.

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