update_campaign_budget

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

No annotations are provided. The description hints at guarded write and preview/validate behavior through the 'preview' and 'dry_run' parameters, and mentions audit logging with 'reason'. However, it lacks details on permissions, reversibility, or rate limits.

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 very short (two sentences), efficient, and front-loaded with the action. However, the brackets notation ('[Ads / guarded write]') is somewhat cryptic. Overall, it is concise but could be more informative.

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?

Despite 5 parameters and no output schema, the description fails to explain key aspects: what the 'changes' array should contain, the difference between preview and dry_run, or which campaign type this tool applies to. The tool's complexity (flexible schema with additionalProperties) demands more explanation.

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 100%, so baseline is 3. The description adds little beyond parameter names; it does not explain the 'changes' array structure or differentiate 'preview' from 'dry_run'. The description's mention of preview/change aligns with the parameters but adds minimal value.

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 states the tool's action ('Preview or change daily campaign budget') and resource ('daily campaign budget'). It also identifies as an ads tool via '[Ads / guarded write]'. However, it does not distinguish between campaign types (SP, SB, SD), especially given sibling tools like update_sb_campaign_budget and update_sd_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 description mentions that this is a 'Hosted endpoint only; this local stdio server is an introspection stub', implying it's used via a hosted API. It does not provide guidance on when not to use it or alternatives, such as the more specific sibling tools.

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