google_ads_set_ad_group_cpc_bid

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

Annotations already disclose destructiveHint=true, readOnlyHint=false, and openWorldHint=true, so the safety profile is covered. The description adds useful domain context that the bid is in account currency and only works for manual CPC bidding, but it does not clarify the confirm parameter or other mutation behavior.

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 clauses with no wasted words, and the core action is front-loaded before the applicability constraint.

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?

This is a destructive mutation with five parameters and zero schema description coverage. Although an output schema exists and annotations cover safety, the description leaves key operational details such as the role of confirm and login_customer_id unaddressed.

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 description coverage is 0%, so the description must carry parameter meaning. It only clarifies cpc_bid as a max CPC bid in account currency; it does not explain customer_id, ad_group_id, login_customer_id, or confirm.

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 states a specific verb and resource: setting an ad group's max CPC bid. It is clear what the tool does, but it does not explicitly distinguish this tool from sibling mutation tools such as google_ads_set_campaign_budget.

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 phrase 'Only applies to manual CPC bidding' gives an important validity condition, but the description does not say when to choose this tool over alternatives or what to do for non-manual bidding.

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