delete_broadcast

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

Annotations already indicate destructiveHint true and idempotentHint true. The description adds important behavioral context by stating the state precondition for deletion, which is beyond what annotations provide. It does not disclose additional side effects or error behavior, but the state condition adds meaningful transparency.

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?

The description is a single sentence that conveys the essential information without any waste. Every part is necessary, and the key constraint is front-loaded. No unnecessary details or repetition.

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 the tool's simplicity (one parameter, no output schema, annotations present), the description is mostly complete. It could benefit from noting that deletion is permanent and what happens if a non-draft/scheduled broadcast is targeted (error message or no-op), but the current description covers the primary constraint. Minor gap, so 4.

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 100%, with the parameter 'id' described as 'The resource ID'. The description adds no further parameter semantics. Baseline of 3 is appropriate as the schema already handles parameter documentation.

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 verb 'delete' and resource 'broadcast', adding a specific scope constraint that only drafts and scheduled broadcasts can be deleted. This distinguishes it from sibling tools like 'create_broadcast' or 'update_broadcast' and provides clear purpose.

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 gives a clear condition for when the tool is applicable (only drafts and scheduled broadcasts), which guides usage. However, it does not explicitly mention when not to use it or suggest alternatives (e.g., for sent broadcasts). That context is implicitly missing, so a score of 4 is appropriate.

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