delete_broadcast

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

Since no annotations are provided, the description carries the full burden. It indicates a destructive action ('delete' and 'clean Redis keys') but does not disclose reversibility, scope of cleanup, or behavior if the broadcast is active or already deleted.

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?

Single sentence with no wasted words. Front-loaded with the key action. However, it could benefit from a brief note on required state.

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?

Given no output schema and minimal parameter information, the description is insufficient for a destructive tool. It lacks details on error conditions, idempotency, and what 'clean Redis keys' entails. Sibling tools suggest related operations but no differentiation is provided.

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 compensate. It does not explain the meaning or source of 'botid' or 'broadcastId' beyond the parameter names. No additional semantics are provided.

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?

The description clearly states the action (delete) and the resource (broadcast tracking record) with an additional detail about cleaning Redis keys. It distinguishes from siblings like stop_broadcast and modify_broadcast by specifying 'completed or stopped' broadcasts.

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?

No guidance on when to use or when not to use this tool vs alternatives. It does not mention that broadcasts must be completed or stopped before deletion, nor does it exclude active broadcasts. No context about prerequisites or side effects.

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