Remove Contact

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

With no annotations, the description fully discloses the destructive, irreversible nature of the operation and the required confirmation workflow. It also explains how to identify the contact (name and email) during the double-check, adding behavioral context beyond the basic 'remove' action.

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 concise and front-loaded: the first sentence states the action, and the next two provide critical safety instructions. Every sentence earns its place without redundancy.

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 tool with no annotations and no output schema, the description covers all essential context: what it removes, how to identify the contact, the irreversible nature, and the required confirmation. It is complete for an agent to invoke safely and correctly.

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?

The input schema already describes both parameters (id and email) with 100% coverage, so baseline is 3. The description adds that the contact can be removed by either ID or email, and that the double-check references the email, providing mild additional context for parameter usage.

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 contact from Resend (by ID or email)', with a specific verb and resource. It distinguishes from sibling tools like update-contact or get-contact by explicitly focusing on removal.

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 provides explicit usage prerequisites: 'you MUST double-check with the user', 'warn the user that removing a contact is irreversible', and 'You may only use this tool if the user explicitly confirms'. This clearly frames when to use and when not to use the tool.

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