Set Campaign Manual Cpc

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

With no annotations available, the description carries the full behavioral burden. It discloses meaningful effects — manual CPC with no enhanced CPC and ad group bids applying again — but omits important operational details like confirmation requirements, permissions, and whether the change affects all specified campaigns at once.

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 front-loaded sentence with no wasted words. It is efficient, though its terseness leaves little room for the usage and confirmation guidance an agent needs for a mutation tool.

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?

Given that this is a mutation tool with no annotations, no parameter descriptions, and a confirm_token field, the description is under-specified. The output schema covers return value information, but the description still lacks the procedural and safety context needed to invoke the tool correctly.

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 explain the parameters. It only vaguely implies campaign targeting through 'campaigns' and does not explain customer_id or the optional confirm_token, leaving two of three parameters without added meaning.

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 action ('Switch campaigns to manual CPC') with a clear resource and mode, and clarifies an important consequence ('ad group bids apply again'). It does not explicitly distinguish itself from sibling tools such as set_campaign_budget, but the core purpose is clear.

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 implies when the tool is useful by naming the target bidding mode, but it gives no explicit when-to-use or when-not-to-use guidance, no alternatives, and no mention of prerequisites such as the confirm_token flow.

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