update_budget

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

No annotations are provided, so the description carries full burden. It discloses the unit conversion but does not mention immediate application, budget limits, idempotency, or side effects. More behavioral details are needed for a mutation tool.

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?

Single sentence with no wasted words. It efficiently conveys the core action and unit conversion. Could include additional context without losing conciseness.

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 3 parameters, 0% schema coverage, and no annotations, the description is insufficient. It lacks details on budget constraints, immediate effect, and behavior when campaign is paused. Output schema exists but does not compensate for missing behavioral context.

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 description must compensate. It explains new_budget_dollars is in dollars and converted to micros, adding value. However, campaign_id and customer_id are not explained; customer_id is optional with default null but purpose is unclear.

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 'Set a campaign's daily budget' with the verb 'set' and resource 'campaign's daily budget'. It also explains the unit conversion from dollars to micros. However, it does not differentiate from sibling tools like pause_campaign or enable_campaign, though they are distinct actions.

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?

No guidance on when to use this tool versus alternatives. It does not mention prerequisites (e.g., campaign must exist) or when not to use it. Sibling tools are for different actions (pausing, enabling, adding keywords), but no explicit comparison.

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