kaiten_delete_api_key

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

No annotations are provided, so the description carries the full burden of behavioral disclosure, but it only repeats the destructive intent already visible in the name. It does not mention that deletion is permanent/irreversible, whether active API access is immediately revoked, or what permissions are required.

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 a single declarative sentence with no filler, and the action is front-loaded. This is appropriately sized for a tool with one required parameter and no nested objects.

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 one-parameter delete operation, the core invocation is covered by the schema and the clear action statement. However, because this is a destructive operation with no annotations and no output schema, the description would be stronger if it noted irreversibility or the effect on active API keys.

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 100%, and the only parameter key_id is clearly described as 'API key ID'. The description adds no extra parameter detail, but none is necessary because the schema fully documents the single required input.

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 states a specific verb ('Delete') and a specific resource ('API key'), which precisely distinguishes it from sibling tools like kaiten_list_api_keys, kaiten_create_api_key, and other delete_* tools. The action is unambiguous and complete.

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 gives no guidance on when to use this tool, no mention of obtaining the key_id first via kaiten_list_api_keys, and no exclusions or alternatives. Usage context is only implied by the verb and resource, not explicitly stated.

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