Delete a sequence email

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 structurally. The description adds genuinely useful consequence detail ('May affect delivery, audience membership, published data or irreversible state') plus the confirm precondition, which goes beyond what the annotations state.

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 short sentences with the core action and the confirm requirement front-loaded and no filler. Every clause carries actionable information.

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 delete with no output schema, the description covers the key facts an agent needs: what it does, the impact surface, and the confirm guard. It stops short of noting cascading effects on subscribers or whether the operation is recoverable, but it is otherwise sufficient.

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 all four parameters (account, confirm, email_id, sequence_id) are already documented in the schema. The description only restates the confirm=true requirement, adding little syntax or semantic detail beyond the structured fields — 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?

States a specific verb+resource combination ('Delete a sequence email') that is unambiguous on its own. It does not, however, differentiate itself from closely related siblings such as delete_sequence or update_sequence_email, leaving the agent to infer the scope from the name.

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 requirement 'confirm=true' gives a concrete precondition for invocation, and the schema clarifies it should only be used for user-requested actions. However, there is no guidance on when to delete vs. update or unpublish a sequence email, nor any reference to alternatives.

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