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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is covered. The description adds genuinely useful scope detail: published posts survive, and the parent campaign is paused as a side effect (an effect the tool name omits). It does not say whether the pause or the cancellation 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?

Two tight sentences with no filler; the destructive scope is front-loaded and the survival clause follows immediately where it is most needed.

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 one-parameter destructive mutation whose annotations already carry the safety hints and with no output schema to explain, the description covers what changes and what does not. Only reversibility and the post-call state of the campaign are unstated.

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 coverage is 100% and the single parameter already documents that it accepts an id or a name. The description adds nothing about the identifier, so the baseline of 3 applies.

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?

Names specific verbs and resources: pauses a campaign and cancels its unpublished posts. The scope sentence ('has not gone out yet') sharpens it well beyond the title. It never names the near-siblings pause_campaign or delete_campaign, so differentiation is left implicit.

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 makes the effect clear enough that its use case is implied: cancel the not-yet-published backlog. However, it gives no explicit guidance on when to choose this over pause_campaign or delete_campaign, which are the obvious alternatives in the sibling list.

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