remove

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

Without annotations, the description must convey critical behavioral traits. It explicitly states 'permanently delete,' indicating irreversibility. However, it does not describe any side effects, required permissions, or what happens to related data, leaving gaps 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 a single sentence with no wasted words. However, it is so brief that it sacrifices completeness; a slightly longer description front-loading essential details would be more effective without sacrificing conciseness.

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 complete in terms of purpose, but for a destructive operation without annotations, more behavioral context is expected. The description lacks details on what the deletion entails, making it incomplete for safe use.

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 description mentions 'item' as the target, weakly linking to the 'key' parameter. With 0% schema description coverage, the description should explain the meaning of 'key' (e.g., what format, where to obtain it), but it adds only minimal context. The agent cannot determine how to specify the item beyond guessing it's a string identifier.

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 'permanently delete an item from the vault,' which is a clear verb+resource combination. It distinguishes from siblings like fetch (retrieval) and store (insertion), leaving no ambiguity about its purpose.

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 tool versus alternatives. The description does not mention prerequisites, contexts where deletion is appropriate, or cases where it should be avoided. The agent is left to infer usage from the tool's name and siblings.

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