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

Annotations already declare idempotentHint=true and destructiveHint=false, so the safety profile is partly covered. The description adds real behavioral information beyond that: pausing stops new dials but lets in-flight calls complete, meaning the effect is gradual rather than an immediate hard stop — exactly the kind of consequence an agent needs before calling it mid-run.

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 compact sentences, zero filler, with the operational effect front-loaded before the handoff to the resume tool. Nothing could be removed without losing information.

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 idempotent state-toggle with a fully described schema and no output schema, the description supplies everything needed: what it does to traffic, what happens to live calls, and the next tool to call. No return-value explanation is owed.

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 broadcast_id, reason, and purpose are all documented in the schema itself. The description adds no additional meaning about parameter usage or formats; baseline 3 applies since the schema does the work.

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 broadcast') and immediately defines the operational boundary — no new dials start, in-flight calls finish. That distinguishes it clearly from resume_broadcast and from the dialer-campaign siblings without needing to open any schema.

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?

Explicitly routes the agent to resume_broadcast as the follow-up action, so the pause/resume pairing is unambiguous. It stops short of stating when NOT to pause (e.g., versus pause_dialer_campaign for campaign-level stops), but the context of use is clear.

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