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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is covered. The description adds real value beyond that by distinguishing plain cancellation from the more aggressive `remove: true` deletion, but it does not state irreversibility, effects on already-sent broadcasts, or auth requirements.

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?

A single sentence, front-loaded with the primary action and immediately qualifying the alternate mode. Nothing is wasted and nothing is buried.

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 destructive, no-output-schema mutation tool, the description is thin: it omits what happens if the broadcast has already gone out, whether the action is reversible, and any required permissions. Annotations carry the danger signal, but the operational context an agent needs for a destructive call is only partially present.

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 coverage is only 33%, with the idempotencyKey documented and `remove` undocumented. The description compensates by explaining exactly what `remove: true` does, and broadcastId is self-evident from its name, so the meaningful semantic gap is closed.

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/delete) and resource (broadcast), and the remove flag makes the two modes explicit. It is readily distinguishable from siblings like list_broadcasts, create_broadcast and send_broadcast, though it does not name any of them.

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 description implies use for a scheduled broadcast and clarifies the cancel-vs-delete choice via `remove: true`, which is genuine usage guidance. However, it gives no prerequisites (e.g., must the broadcast still be scheduled?), no exclusions, and no comparison to neighboring lifecycle tools.

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