zernio_delete_api_key

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

The description indicates irreversibility ('permanently delete'), which is a key behavioral trait. However, it does not disclose potential side effects (e.g., services using the key will stop working), and there are no annotations to supplement this. The description is minimal but covers the essential mutation nature.

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 concise—exactly one sentence. It is front-loaded with the action. While it could include slightly more detail, it is not verbose and conveys the core purpose effectively.

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 simple tool with one parameter and no output schema, the description is adequate but not complete. It does not mention what happens after deletion (e.g., confirmation, error handling) or the impact on existing API usage. The description feels minimal but covers the basic action.

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 single parameter `keyId` is well-described in the input schema ('The API key ID to revoke'). The tool description adds no further meaning beyond that. With 100% schema coverage, the baseline is 3, and the description does not improve upon it.

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 'Revoke and permanently delete an API key' clearly states the action (revoke and delete) and the resource (API key). It distinguishes itself from sibling tools like `zernio_create_api_key` and `zernio_list_api_keys` by indicating it is for deletion only.

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 usage guidance is provided. The description does not mention when to use this tool (e.g., after obtaining the key ID from `zernio_list_api_keys`) or when not to use it. There are no prerequisites or alternative suggestions.

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