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

Annotations already declare it is a non-read-only, non-destructive, non-idempotent mutation, and the description adds real context: the observable effect ('Delivery stops until you resume it') and the state gate ('only sending broadcasts'). It does not say what happens on a repeat call or on a non-sending broadcast, which matters given idempotentHint=false.

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, front-loaded with the action and with no filler. 'Currently sending' and 'only sending broadcasts can be paused' partially restate the same precondition, a small redundancy that keeps it just short of ideal.

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 single-parameter state-mutation tool with no output schema and full annotation coverage, the description supplies the precondition, the delivery effect, and the recovery path. The main omission is failure behavior (repeat pause, wrong-state broadcast) on a tool flagged non-idempotent.

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?

Only one parameter with 100% schema description coverage, so the schema already documents broadcast_id as the UUID of the sending broadcast. The description's state constraint slightly narrows which UUID is valid but adds no syntax or format detail beyond the schema. Baseline 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?

States a specific verb ('Pause') and resource ('broadcast') with scope ('that is currently sending'). It also names the inverse sibling meisa_resume_broadcast, letting an agent distinguish pause from resume, cancel, or delete without opening schemas.

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?

Gives an explicit precondition ('Only sending broadcasts can be paused') which implicitly excludes draft/scheduled/cancelled ones, and points to the resume tool for the reverse action. It stops short of contrasting with siblings like cancel_broadcast, which is a plausible alternative when an agent wants to stop delivery permanently.

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