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

The description supplies rich behavioral detail absent from the annotations: hard guardrails (+50% per change, +100% cumulative per 24h, -80% max cut) and a preview/apply confirm flow. This meaningfully warns the agent about mutation limits beyond destructiveHint=true.

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?

Three compact sentences, front-loaded with the action and guardrails before the confirm mechanics. Every sentence carries weight; nothing is padded.

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?

With an output schema present, return values need no explanation, and the guardrails plus confirm semantics cover the critical call requirements. Minor gaps remain around the customer_id vs account_id distinction.

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 the description must compensate. It explains the confirm parameter's two modes clearly, but adds no meaning for account_id, campaign_id, customer_id, or daily_budget beyond self-evident names, leaving the customer_id purpose undocumented.

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?

States a specific verb (Updates) and resource (a campaign's daily budget) so an agent knows exactly what changes. It is platform-scoped to Microsoft via the name and cross-references Google/Meta/LinkedIn/TikTok guardrails, though it never contrasts with the close sibling set_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 confirm=false/confirm=true preview-vs-apply rule is useful workflow guidance, but there is no explicit when-to-use guidance relative to set_campaign_budget or other budget tools. Usage is implied rather than stated.

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