Delete a broadcast

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 covered. The description adds real value beyond that by naming the blast radius ("delivery, audience membership, published data or irreversible state") and restating the confirm gate, which tells the agent this is not a recoverable cleanup.

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 with zero filler; the action is front-loaded and the consequence and precondition follow in priority order. Every sentence carries distinct information.

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 mutation with full annotation coverage and no output schema, the description covers action, consequences, and the confirm gate, which is what an agent needs to call it correctly. Only minor gaps remain, such as what happens on a broadcast that is mid-send or already deleted.

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 description coverage is 100%, so account, confirm, and broadcast_id are already documented in the schema, including the confirm semantics. The description echoes the confirm requirement but adds no format, id-type, or account-resolution detail beyond what the schema provides.

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 and resource ("Delete a broadcast"), which cleanly separates it from sibling deletes like delete_sequence_email, delete_sequence, and delete_webhook. It does not explicitly name a sibling or scope boundary, but the resource is unambiguous.

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 supplies a precondition ("Requires confirm=true"), which is genuine usage guidance. However, it never says when to prefer this over update_broadcast or what state a broadcast must be in to be deletable, so the when-to-use context is only implied.

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