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

Annotations already declare idempotentHint=true and destructiveHint=false, but the description adds real behavioral detail: no new calls are released while in-flight calls complete, and it is safe to invoke at any point. That is exactly the side-effect profile an agent needs before pausing a live dialer; only the resulting campaign state is left implicit.

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 short sentences with the core action and its side effect front-loaded, followed by the safety note. No filler or redundant restatement of the tool name.

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 simple single-parameter state-change tool with full schema coverage and annotations covering safety, the description supplies the missing piece (what happens to queued and in-flight calls). Only the post-pause campaign status and the recovery path 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 description coverage is 100%, so campaign_id and purpose are already documented in the schema. The description adds nothing about parameter meaning, which is the expected baseline when the schema does the heavy lifting.

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 and resource (pause a running campaign) plus the operational effect, so an agent can tell it apart from resume_dialer_campaign. It doesn't explicitly name the sibling alternatives like pause_broadcast, leaving a small ambiguity between dialer campaigns and broadcasts.

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?

"Safe to call at any time" gives a useful precondition hint (no state guard needed), and "running campaign" implies when it applies. However, there is no explicit when-to-use/when-not guidance and no pointer to resume_dialer_campaign or pause_broadcast as alternatives.

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