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 known. The description goes beyond them by naming the blast radius ('delivery, audience membership, published data or irreversible state') and the confirm gate, which is genuine added value. It stops short of saying whether the deletion cascades to sequence emails or enrolled subscribers.

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?

Three terse sentences with zero filler; the action, the impact, and the hard prerequisite are all front-loaded. Nothing here could be cut without losing meaning.

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, non-idempotent tool with no output schema, the combination of annotations (safety) plus the description's impact list and confirm requirement covers most of what an agent needs. The remaining gap is scope: it never clarifies whether sequence emails or subscriber enrollments are also removed.

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 already documented in the schema. The description only echoes the confirm requirement and adds no format or constraint detail beyond it, making the baseline 3 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?

States a specific verb and resource ('Delete a sequence'), so the operation is unambiguous. However, it does not distinguish itself from the sibling delete_sequence_email, and an agent could plausibly confuse whole-sequence deletion with deleting a single email in a sequence.

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 supplies one real prerequisite ('Requires confirm=true'), which is useful gating information. But it offers no when-to-use/when-not guidance and never mentions the sibling delete_sequence_email as the narrower alternative, leaving the agent to infer which deletion tool fits the request.

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