delete_broadcast

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

With no annotations, the description carries the full burden of behavioral disclosure. 'Deletes' implies a destructive action, but it does not disclose whether the deletion is permanent, cascades to associated content (e.g., messages, members), or requires special permissions. This lacks context beyond the basic operation, similar to the update_drive calibration example.

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 clear sentence with no redundant words. It fully captures the tool's purpose in the minimal space needed, earning full marks for conciseness and structure.

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?

The tool is simple (one parameter), but the lack of annotations and output schema means the description must cover side effects. It does not mention whether deletion is permanent, what happens to members/content, or what is returned. For a destructive action, this is incomplete, warranting a score of 2.

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?

The input schema fully documents the single parameter list_id with a description 'Broadcast list ID to delete', achieving 100% coverage. The tool description adds no additional parameter meaning beyond what is already in the schema, so the baseline of 3 is appropriate.

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?

Description states the specific action 'Deletes' and the resource 'broadcast list', clearly distinguishing it from sibling tools that delete other resources (e.g., delete_channel, delete_message). The verb is precise and 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 provides no guidance on when to use this tool versus alternatives, such as remove_broadcast_members for removing individual members or rename_broadcast for altering the list. It does not state any prerequisites, exclusions, or comparisons to similar deletion tools, leaving the agent to infer usage from the name alone.

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