Delete alias contact

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

Annotations declare destructive/irreversible, but the description goes further by spelling out the concrete consequences: the reverse-alias address stops working and the correspondence history is removed. It also states the required confirm=true acknowledgement, adding context the annotations do not carry.

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 sentences, front-loaded with the destructive action and consequence, then the safer alternative, then the guardrail. No filler or repetition.

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, no-output tool with full annotation coverage, the description supplies everything an agent needs: irreversibility, data loss scope, the alternative path, and the confirmation guard.

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 coverage is 100% and both parameters are already documented in the schema, including the const:true semantics of confirm. The description only restates the acknowledgement requirement, adding little beyond structured data.

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 (permanently delete), resource (contact / reverse alias), and identifier type (numeric id). It is immediately distinguishable from siblings like contact_set_blocked or alias_delete.

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?

Explicitly routes the agent: 'To merely stop receiving mail from the contact, prefer contact_set_blocked with blocked=true instead.' It names the alternative and the condition that selects it, plus the confirm=true prerequisite.

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