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

Annotations already declare readOnlyHint=false, destructiveHint=true and openWorldHint=true, so the safety profile is partly covered. The description still adds value with the [WRITE — changes your live account] banner, the concrete consequence 'Pausing stops spend', and the confirm gate — real effects rather than restated hints. It does not mention reversibility, propagation delay, or rate limits.

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 sentences, with the most important fact (this mutates a live account) front-loaded in a bracketed banner. Nothing is redundant or 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?

For a destructive mutation with no output schema, the description correctly conveys effect, target level, and the confirmation requirement, and the annotations plus rich schema cover the rest. It is slightly thin on what a successful call returns or whether the change is instantly reflected.

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 100% and every parameter (level, status, confirm, object_id, customer_id) is documented in the schema, so the baseline is 3. The description only echoes the status and confirm semantics already present in the schema, adding no new parameter detail.

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 pair (pause/resume) and the exact resource scope (a campaign or ad group by id), which is clearly narrower than google_ads_update_campaign/ad_group. It does not explicitly say why to prefer this over passing a status field to the update tools, so sibling differentiation is implied rather than stated.

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 implies the use case (stop or restart spend) and flags that confirm:true is required, but it gives no when-not guidance and names no alternative tool. An agent must infer that bulk/create/update operations belong to the sibling google_ads_* tools.

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