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

Annotations already declare destructiveHint=true, idempotentHint=false, readOnlyHint=false, so the safety profile is covered. The description adds real behavioral context beyond them: the two-phase preview/apply gate controlled by confirm, which is not derivable from the annotations. It still doesn't say what side effects apply to child ads/budgets or what auth is required.

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 telegraphic fragments, front-loaded with the core action and with zero filler. The style is terse enough to be slightly clipped, but every clause carries information and nothing is wasted.

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?

An output schema exists, so return values need not be described. For a destructive mutation tool the description covers the key gating behavior and allowed enum values, but it omits the meaning of the remaining identifiers and any note on scope or reversibility. Adequate but not full.

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, and it partially does by documenting the status values (Active | Paused) and the confirm semantics. However, account_id, campaign_id, and customer_id — three of five parameters, including two required ones — receive no explanation in either the schema or the description.

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+resource ("Changes campaign status") and the Microsoft scoping in title, so an agent can distinguish it from update_microsoft_ad_status or update_microsoft_ad_group_status. It does not, however, differentiate itself from the nearby update_campaign_status or pause_campaign siblings, so the platform/level distinction is left to inference.

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 gives a genuine usage pattern for the confirm flag ("confirm=false = preview, confirm=true applies"), which tells the agent to preview before committing. It offers no when-to-use guidance relative to alternatives such as pause_campaign or update_campaign_status, and no prerequisites or exclusions.

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