delete_api_key

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

The description implies a destructive action but provides no details on permanence, side effects, or required permissions. With no annotations, the burden is on the description, and it fails to disclose critical behavioral traits.

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?

While extremely short (3 words), the description is under-specified and provides no structured information. Conciseness should not sacrifice essential context; it does not earn its place.

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 tool's simplicity (one required param, output schema exists), the description is wholly incomplete. It omits return value, effect on system, and any post-condition, making it insufficient for an agent to use correctly.

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 input schema has one parameter (key_id) with 0% description coverage. The description offers no explanation of this parameter, leaving the agent without semantic guidance for its value.

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 'Delete API key' restates the tool name without adding new information. It identifies the action and resource but lacks specificity about which API key or context.

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 provided on when to use this tool, prerequisites, or alternatives. The description does not help distinguish from other deletion or key management tools among siblings.

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