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

Annotations already declare destructiveHint=true and openWorldHint=true, but the description adds meaningful context beyond them: immediate ('NOW') execution, all-recipient reach, and public-facing impact, plus a required user-confirmation step. It does not contradict the annotations.

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 tight sentences, no filler. The immediacy and confirmation warning are front-loaded, which is exactly what an agent needs before acting.

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 tool whose annotations cover the safety profile, the description supplies the irreversibility, reach, and confirmation requirement. It omits any hint about the required broadcastId source or the relationship to create_broadcast/list_broadcasts, leaving a small gap.

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 50%: idempotencyKey is documented in the schema, but broadcastId is undocumented in both schema and description. The description mentions no parameters at all, so it fails to compensate for the coverage gap on the required broadcastId.

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?

Specific verb (Send) plus resource (broadcast) with immediate scope ('NOW to every recipient'). Clearly distinguishable from siblings like create_broadcast, cancel_broadcast, and list_broadcasts, which do not deliver the broadcast.

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 a clear precondition: 'always confirm with the user before calling it.' This tells the agent when it is appropriate to invoke the tool. It stops short of naming alternatives (e.g., create_broadcast to set one up) or explicit conditions for when not to send.

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