update_ad_group_bid

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

The description proactively discloses that the tool performs a dry run by default, requiring confirm=True to execute the change. This is critical behavioral context beyond the tool name, especially given no annotations are present. It does not cover return behavior or permissions, but the dry run disclosure is substantial.

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 a single, information-dense sentence front-loaded with the action verb and object. It contains no redundant phrases.

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?

The description covers the core purpose and the crucial dry-run default, but lacks details about expected return values, side effects of confirmation, and parameter semantics for the IDs. Given no output schema and no annotations, it leaves moderate gaps for an agent.

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?

The description adds semantic meaning to cpc_bid_micros ('in micros') and confirm ('Dry run unless confirm=True'), but leaves customer_id and ad_group_id unexplained. With 0% schema description coverage, it only partially compensates for the missing parameter documentation.

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 changes an ad group's default max CPC bid, with the unit (micros) specified. It uniquely identifies this operation among sibling tools, none of which handle bid updates.

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 provides clear context that this is an update operation for bids. The 'Dry run unless confirm=True' guidance tells when actual changes happen. However, it does not explicitly compare to alternative tools or state when not to use it.

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