update_campaign_budget

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

With no annotations, description carries full burden. Discloses that operation is a mutation, that it previews unless confirm=true, that changes are capped, and that it resolves a shared budget resource first. These are important behavioral traits beyond simple action.

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?

Two sentences, first sentence captures core purpose and state-change mode, second adds internal resolution step. Zero waste, front-loaded.

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 output schema exists, description covers key behaviors. However, it lacks details on error handling or what happens when cap exceeded, but these may be in output schema. Still reasonably complete for a mutation tool.

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%. Description explains amount_micros (micros for daily budget) and confirm (previews unless true), but does not detail customer_id or campaign_id. Partially compensates but incomplete.

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 explicitly states 'Set a campaign's daily budget (micros)' with clear verb ('set') and resource ('campaign's daily budget'). It distinguishes from sibling tools like update_ad_group_bid by specifying it's for campaign budget. The nuance of preview vs confirm further clarifies.

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?

Provides guidance on preview behavior and capping, and mentions resolving shared budget resource. However, it does not explicitly compare to sibling tools or state when to use this vs create_campaign or pause_campaign.

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