Remove API Key

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

With no annotations provided, the description carries full responsibility for disclosing behavioral traits. It states that removing an API key is 'irreversible and any services using it will lose access', and requires user double-check and explicit confirmation. This transparently communicates the destructive nature and the need for consent.

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 efficient and front-loaded: it states the core action first, then provides necessary safety instructions. Every sentence serves a purpose—setting the action, requiring double-check, warning about irreversibility, and conditioning on explicit confirmation. No unnecessary 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?

The description covers the destructive nature, user confirmation requirement, and the need to reference the API key name. While it omits details like error handling or permissions, the safety-critical aspects are thoroughly addressed. Given no annotations or output schema, this is a complete enough description for safe invocation.

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 schema already provides 100% coverage for the single 'id' parameter with description 'API key ID'. The tool description adds minimal extra meaning, only reinforcing 'by ID' and referencing the name for double-checking. Since schema coverage is high, the baseline of 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 an API key by ID from Resend.' This specifies the verb (remove), resource (API key), and scope (by ID). It distinguishes from sibling tools like create-api-key and list-api-keys. The purpose is unambiguous.

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 protocol: 'Before using this tool, you MUST double-check with the user...' and 'You may only use this tool if the user explicitly confirms...'. It gives clear instructions on when to use the tool and the required confirmation steps, effectively guiding the agent on safe usage.

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