delete_key

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

The description provides no behavioral disclosures beyond the fact of deletion. No annotations exist to compensate. Critical details like irreversibility, permissions needed, or effects on related data are omitted, which is essential for a destructive operation.

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 extremely short but lacks necessary detail. While concise in length, it fails to provide enough information to guide correct usage, making it under-specified rather than efficiently succinct.

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?

With no annotations, no output schema, and a single parameter lacking description, the description is highly incomplete. It does not explain return values, error conditions, limitations, or behavior with non-existent 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?

The input schema has one parameter 'keys' with no description. The tool description does not add any meaning beyond the schema, leaving the parameter's purpose and constraints entirely implicit.

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 one or more keys' clearly states the action and resource, making the purpose understandable. However, it does not differentiate from sibling tools like rename_key or set_ttl, which also operate on keys.

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 is provided on when to use this tool versus alternatives such as rename_key or other deletion tools. The description lacks context for appropriate usage.

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