Delete a sequence

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

Annotations already declare destructiveHint=true and idempotentHint=false, so the safety profile is covered. The description earns credit by going beyond that to disclose the blast radius ('may affect delivery, audience membership, published data or irreversible state'), which tells the agent what downstream state is at risk.

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?

Two tight sentences with zero waste; the core action is front-loaded and the risk note plus confirm requirement follow immediately. Nothing is padding.

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 destructive mutation with no output schema, the description supplies the necessary warning about irreversible effects and the confirmation requirement. It stops short of addressing scope (what gets deleted with the sequence) or permission requirements, but the essentials an agent needs are 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%, so account, confirm, and sequence_id are all already documented in the schema itself. The description restates the confirm=true requirement without adding format or constraint detail beyond what the schema provides, so baseline 3 applies.

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?

States a specific verb ('Delete') and resource ('sequence'), so an agent can separate it from delete_broadcast, delete_custom_field, and delete_sequence_email. It does not explicitly differentiate itself from the closely related delete_sequence_email sibling, which is the main residual gap.

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 notes that confirm=true is required, which is a usage condition, but gives no guidance on when to choose this tool over alternatives such as delete_sequence_email or how sequences relate to deletion scope. No when/when-not framing is present.

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