update_ad_group_bid

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

The description mentions preview behavior and a cap, but does not detail what happens if bid exceeds the cap, permissions required, or other side effects. With no annotations, this is adequate but not thorough.

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 two short sentences with no superfluous words, effectively communicating the core action and key behavioral note.

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 bid update tool with an output schema, the description covers the primary functionality and preview behavior. The term 'capped' is vague but not critical; overall it is sufficient for correct 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?

Although the schema properties have no descriptions, the tool description explains cpc_bid_micros (via 'max CPC bid (micros)') and confirm ('Previews unless confirm=true'). However, customer_id and ad_group_id remain unexplained, so some gaps persist.

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 'Set' and the resource 'ad group's default max CPC bid (micros)', specifying the unit. This is specific and distinguishes from sibling tools like update_keyword_bid.

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 explains that the tool previews unless confirm=true, but does not provide guidance on when to use this tool versus alternatives such as update_keyword_bid or enable_ad_group.

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