delete_api_key

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

No annotations provided; the description only adds 'permanently' to indicate irreversibility. It does not disclose other behavioral traits such as authorization requirements, cascading effects, or whether the deletion is immediate.

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 very short and front-loaded, but it omits necessary detail. For a simple tool it is acceptable, but could be slightly improved by adding context about consequences.

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 the existence of an output schema and a sibling 'revoke_api_key', the description fails to provide enough context for proper tool selection. It does not mention return values or when permanent deletion is appropriate.

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 description coverage is 0%, meaning the schema provides no documentation for 'key_id'. The description does not compensate by explaining the parameter's purpose (e.g., which key ID to use).

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?

Description states 'Delete an API key permanently', clearly identifying the action (delete) and resource (API key). However, it does not differentiate from the sibling 'revoke_api_key', which might have a similar purpose.

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?

No guidance on when to use this tool versus alternatives like 'revoke_api_key'. The description lacks usage context or constraints, leaving the agent to guess when permanent deletion is appropriate.

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