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 disclosing the conflict behavior for scheduled/sent broadcasts, though it says nothing about failure on an already-deleted ID or any cascade effects.

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 with no filler, and the primary scope constraint is front-loaded ahead of the edge-case caveat.

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 single-parameter destructive mutation with no output schema, the definition covers purpose, scope, and the main failure mode. Missing only the source of the broadcast ID and behavior on repeat deletion, which are minor given annotation coverage.

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 0%, so the description would ideally explain where broadcast_id comes from (e.g., list_broadcasts) or its format. It adds no parameter meaning, but the single self-named identifier parameter limits the practical cost of that omission.

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 (delete) and resource (broadcast) plus a meaningful scope restriction (draft only). This clearly separates it from siblings like delete_campaign, set_broadcast_status, and update_broadcast, so an agent can select it without opening another schema.

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?

Explicitly states when the tool applies (draft broadcasts) and when it does not (scheduled or sent broadcasts, which produce a conflict). It stops short of naming the alternative action an agent should take instead of deleting a live broadcast, so a small gap remains.

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