Remove Domain

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

No annotations are provided, so the description bears full responsibility. It discloses that removal is irreversible, stops all email sending/receiving for the domain, and requires a specific confirmation protocol. This goes well beyond a generic 'Removes a domain' and gives the agent essential safety context.

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 compact and front-loaded with the action. Every subsequent sentence adds crucial safety information, and there is no redundant wording. It is appropriately detailed for a destructive operation.

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?

Given a single-parameter tool with no output schema and no annotations, the description is remarkably complete. It covers the action, prerequisites, consequences, and the exact consent requirement, providing all necessary guidance for an agent to invoke the tool safely.

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 has one parameter, 'id', with description 'Domain ID' providing 100% coverage. The description merely echoes 'by ID' without adding further semantic detail, so 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?

The description clearly states the action: 'Remove a domain by ID from Resend.' This is a specific verb (Remove) plus resource (domain) and method (by ID). It distinguishes itself from sibling tools like create-domain, update-domain, and verify-domain.

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 preconditions: double-check with the user, warn about irreversibility, and only proceed with explicit confirmation. It states when-not-to-use (without confirmation) but does not mention any alternative tools or methods, so it falls short of a 5.

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