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

Annotations already declare destructiveHint=true and idempotentHint=false, so the safety profile is partly covered; the description goes well beyond by stating the action is irreversible, that it contacts real people, that a mismatched confirmRecipientCount causes refusal, and that cancel is exempt from confirmation. Those are behavioral rules the schema and annotations do not convey.

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?

Four sentences, zero filler, with the irreversible-action warning front-loaded before the procedural requirements. Each sentence carries a distinct rule.

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, non-idempotent action tool with no output schema, the description covers what the tool does, the approval workflow, the count-verification guard, and the cancel exemption. Nothing needed to invoke it correctly is missing.

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 100%, so the baseline is 3, but the description adds real meaning: confirmRecipientCount is required for send/schedule and must equal the live count obtained from add_broadcast_recipients, and cancel needs no confirmation. The cross-tool dependency and refusal condition go beyond the schema's own parameter text.

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 concrete verb set (deliver, schedule, cancel) against a specific resource (broadcast), and the destructive scope is unambiguous. An agent can distinguish this from create_broadcast and delete_broadcast by the send/schedule/cancel framing.

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 explicit when-to-use per action (send = now, schedule = at scheduledAt, cancel = stop a scheduled broadcast) plus the mandatory prerequisite of user approval and confirmRecipientCount. It names add_broadcast_recipients as the source of the count, but never addresses the create_broadcast vs send_broadcast boundary, which is the likeliest sibling confusion given the large sibling list.

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