wafle_ads_campaign_update_budget

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

Annotations include destructiveHint: true, and the description adds that direct calls without following the scaling rule could 'blow the Learning Phase'. It also clarifies that cents are in the ad account currency, adding context beyond the annotations.

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 short paragraphs, front-loaded with the primary action. Every sentence adds relevant operational detail with no filler.

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 tool with four params and no output schema, the description covers purpose, parameter selection, constraints, and a risk warning. It doesn't describe the return payload, but the schema and annotations provide ample structured 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?

The schema already covers all four parameters, but the description adds value by marking daily_budget_cents as preferred and emphasizing the mutual exclusivity constraint, plus the currency clarification.

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 opens with 'Update a Meta campaign's budget', clearly stating the verb and resource. It further specifies the two mutually exclusive budget parameters, distinguishing it from sibling tools like pause/resume.

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?

It identifies daily_budget_cents as preferred and explicitly notes the mutual exclusivity in the Marketing API. It also advises mirroring the recommender's +30% / max +50% rule when calling directly, providing practical guidance on how to use the tool safely.

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