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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so safety is covered. The description adds genuine context beyond that: partial sends will halt mid-flight, the broadcast cannot be resumed, and the action is unrecoverable. That goes further than the annotation set alone.

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 its valid states, followed by consequence and irreversibility. Every sentence carries distinct information and none repeats the title or schema.

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 with no output schema, the description covers applicability, effect on in-flight sends, and irreversibility, which is what an agent needs before invoking. Only the distinction from the reversible pause/resume path is left 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?

There is a single parameter with 100% schema description coverage, so the schema already fully documents broadcast_id including its UUID format. The description contributes no additional syntax, format, or source-of-truth guidance for the identifier, matching the baseline for a fully covered schema.

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 (Cancel) and resource (broadcast) plus the three states in which it applies (scheduled, sending, paused). It implicitly separates itself from meisa_pause_broadcast/meisa_resume_broadcast via 'cannot be resumed', but never names a sibling explicitly, so differentiation is inferential rather than stated.

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 clear context for when the tool applies (a scheduled, sending, or paused broadcast) and adds the crucial constraint that the action is irreversible. It stops short of explicitly routing the agent away from this tool toward the reversible alternative meisa_pause_broadcast when the user only wants a temporary stop.

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