komodo_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. It never states that deletion is irreversible, whether an existing key can be recovered, or what authorization is needed - all critical for a destructive operation. 'Deletion confirmation' is the only behavioral hint and is redundant with the existing output schema.

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?

Short and front-loaded: the core action is the first sentence, with Args/Returns sections kept minimal. The boilerplate Args/Returns scaffolding is slightly wasteful given there is only one parameter and an output schema, but nothing is verbose.

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 destructive tool with no annotations and no guidance, the description is thin. The output schema covers return values, but the absence of any warning about irreversibility, permissions, or side effects leaves the agent without what it needs to invoke this safely.

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%, so the description is the only source of parameter meaning. It does identify key_id as 'ID of the API key to delete', which the bare string schema does not, but adds no format, source, or example detail for the single parameter.

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?

States a specific verb and resource ('Delete an API key'), so an agent can immediately tell it removes a key. It is not differentiated from siblings like komodo_create_api_key or komodo_list_api_keys beyond the name, but the action 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?

No guidance on when to use this versus alternatives, no prerequisites, no mention of required permissions or confirmation. The agent must infer that this is the destructive counterpart to komodo_create_api_key from the name alone.

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