Remove Broadcast

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

No annotations provided, so the description carries the full behavioral disclosure burden. It clearly states that removal is irreversible, which is a critical behavioral trait. However, it does not mention potential side effects (e.g., impact on associated data) or permission requirements, which would provide more completeness.

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 fairly concise with two clear parts: purpose and usage guidelines. Slightly wordy but every sentence provides value. Front-loaded with the primary action.

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 simple removal tool with one parameter and no output schema, the description covers purpose, identification method, and critical usage constraints. It lacks details on return values or error handling, but the essential context for safe invocation is present.

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 100% for the single parameter, so the description adds no additional semantics. The schema already describes broadcastId as accepting an ID or Resend dashboard URL. Baseline 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?

The description clearly states the action 'Remove a broadcast' and specifies how to identify it (by ID or Resend dashboard URL). This verb+resource combination distinguishes it clearly from sibling tools like update-broadcast or send-broadcast.

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?

Provides explicit, actionable guidance: must double-check with user, reference the broadcast name, warn that removal is irreversible, and only proceed after explicit user confirmation. This tells the agent exactly when and how to use the tool, including exclusions.

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