set_campaign_cpc_ceiling

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

With no annotations provided, the description carries the behavioral burden. It discloses that the operation is a dry run unless confirm=true, which is a critical safety behavior, and explains the effect of passing 0. It could add permission requirements or reversibility notes, but the dry-run and removal semantics are well covered.

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?

Three concise sentences deliver the core action, parameter nuance, and confirmation requirement with no filler. The most important behavioral note (dry run unless confirm=true) is placed at the end but is clearly readable and well separated.

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 essential context: target campaign type, parameter semantics, and mutation safety via dry-run. An output schema exists, so return-value details are not required here. Minor gaps like expected value range or whether the ceiling persists across updates do not prevent 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?

Schema description coverage is 0%, so the description must explain parameters. It meaningfully defines cpc_bid_ceiling with currency and zero-removal semantics, and confirm is explained by the dry-run sentence. customer_id and campaign_id are left implicit, but their purpose is self-evident from their names.

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 identifies the action (setting a max CPC bid ceiling), the resource (a campaign using Maximize Clicks / Campaign.target_spend), and the currency context with an example. This distinguishes it from sibling tools like set_campaign_target_cpa and set_campaign_daily_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 description states the specific campaign type this applies to (Maximize Clicks), which is a clear usage condition. It also explains the special case of passing 0 to remove the ceiling. It does not explicitly name alternatives or state when not to use it, but the target_spend constraint is strong guidance.

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