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

Annotations already declare destructiveHint=true, idempotentHint=false and openWorldHint=true, so the safety profile is covered. The description adds value beyond them by disclosing the dry-run/confirm semantics — an agent knows how to preview before committing a destructive change — plus the campaign_id prerequisite. It stops short of saying what the status change affects (delivery halt) or whether it is reversible.

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 short telegraphic sentences, front-loaded with the core action and no filler; every clause carries information. The parenthetical "(campaign_id required.)" is slightly awkward but efficient.

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 no explanation, and the annotations carry the destructive/idempotency profile. Combined with the enum values and confirm preview loop, the description supplies everything needed to call this mutation correctly; only the undocumented id parameters keep it from being exhaustive.

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 does partially: it supplies the status enum values (Active | Paused) that the schema lacks, and explains confirm's true/false behavior. However, account_id, ad_group_id, and customer_id (including its empty-string default) remain undocumented in both places, so the majority of the 6 parameters carry no semantics.

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 an ad group's status") and enumerates the target states, so the agent knows exactly what is mutated. It does not, however, distinguish this from the sibling update_microsoft_ad_group or update_microsoft_ad_status, leaving the agent to infer the boundary from the name alone.

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?

Gives real operational guidance for the two-step flow (confirm=false previews, confirm=true applies) and flags campaign_id as required, which is genuinely useful. But it offers no when-to-use-vs-alternative guidance or exclusions relative to the many sibling status tools, so usage is only implied.

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