Set Campaign Budget (gated mutation)

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

Annotations already indicate destructiveHint=true and readOnlyHint=false. Description adds value by flagging the tool as 'GATED' (implying access restrictions) and warning about the ID confusion. No contradictions.

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?

Extremely concise: two sentences cover the core action, gated nature, and critical ID distinction. No wasted words.

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?

For a single-field mutation tool with an output schema, the description is fairly complete. It explains the purpose, access restriction, and prerequisite discovery step. Could mention that the update takes effect immediately, but not essential.

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 60%, and the description does not add significant meaning beyond what the schema already provides for customer_id, amount_micros, and campaign_budget_id. It mentions campaign_budget_id but doesn't elaborate on other parameters.

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?

Clearly specifies verb "Update" and resource "campaign budget's amount_micros". Explicitly distinguishes from sibling tools by noting the gated nature and the critical distinction between campaign_budget_id and campaign id.

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 clear context: states it's gated (restricted access) and instructs how to discover the correct ID via google_ads_get_campaign. Does not explicitly state when not to use or compare to alternative tools, but the context is sufficient for proper usage.

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