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

Annotations already declare idempotentHint=true, destructiveHint=true, and readOnlyHint=false, so the description's second sentence restating idempotency adds little. The one genuinely additive piece is the effect disclosure — sending stops until resumed — but the description never reconciles that with destructiveHint=true, nor does it say what happens to already-queued messages, what permissions are required, or which tool resumes the campaign.

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 sentences, zero filler, with the core action and its effect front-loaded before the idempotency note. Nothing in the text 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 mutation tool with no output schema and 0% schema coverage, the description covers the intent and the sending-stops effect but leaves the entire parameter story and the reversibility path (which sibling resumes it) undocumented. Adequate as a minimum, but an agent calling it has to guess at the body shape and at how to undo the pause.

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% and the description names neither of the two parameters. The nested `params.id` (uuid) and the untyped `body` object are documented only by their types, so the description does not compensate for the coverage gap; in particular, an agent gets no hint about what `body` accepts for a tool whose payload appears to be just an identifier.

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?

The description gives a specific verb and resource ("Pauses an active campaign") plus the operational consequence ("its sequence stops sending"). It is clear what the tool does, but it never distinguishes itself from the close siblings archiveCampaign, discardCampaign, and restoreCampaign, so an agent must still infer which of the four state-change tools applies.

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 qualifier "an active campaign" implies a precondition (the campaign must be running), which is useful routing information. However, there is no explicit when-to-use/when-not-to-use guidance and no mention of the alternative tools (archiveCampaign, discardCampaign, restoreCampaign) that an agent would need to choose between for other campaign state transitions.

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