Remove API Key

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

Discloses irreversibility and loss of access for services, which is critical. No annotations provided, so description carries full burden. Could mention rate limits or cascading effects, but current detail is sufficient for simple delete.

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?

Concise, front-loaded action, then safety instructions. Every sentence adds value.

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?

Complete for a single-parameter delete tool with no output schema. Addresses safety, prerequisites, and usage constraints.

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 covers 100% with description 'API key ID'. Description adds no extra meaning beyond 'by ID', 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?

Clearly states 'Remove an API key by ID from Resend', specifying verb, resource, and scope. Distinguishes from sibling tools like create-api-key and list-api-keys.

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?

Provides explicit instructions to double-check with the user, warn about irreversibility, and only proceed after explicit confirmation. No alternatives needed since only one remove tool exists.

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