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

Annotations already flag destructiveHint=true, so the bar is lower; the description still adds real value by disclosing the cascading scope of destruction (media, comments, and a derived playbook) and the irreversibility implied by "permanently." It omits auth/ownership requirements beyond the vague "needs its key" and says nothing about confirmation or recovery.

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 with the destructive verb and consequence front-loaded, and the usage trigger appended. The parenthetical slightly interrupts the flow but every clause carries information; nothing is padded.

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 two-parameter destructive tool with no output schema, the description covers what is destroyed and when to reach for it, which is the core need. It leaves the id parameter undefined and never states permissions or whether deletion of a live/owned broadcast has side effects, so an agent still has gaps before calling.

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 must carry both parameters. It only gestures at one — "needs its key" implies the key parameter is mandatory and likely serves as an authorization token — while the id parameter is never explained at all (broadcast identifier? key prefix?).

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 plus resource ("Permanently delete... broadcasts") with an explicit enumeration of what is removed (recording, screenshots, comments, learned playbook). That enumeration does much to separate it from siblings like end_broadcast or review_broadcast, but no sibling is named, so the boundary is inferred rather than stated.

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?

"Use it if something private was shared" gives one concrete triggering scenario, which is more than most definitions offer. It stops short of any when-not guidance or an explicit alternative — notably it never says how this differs from end_broadcast for an agent deciding between stopping and erasing.

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