Delete Vault

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

Beyond the destructiveHint annotation, the description discloses that the action is permanent ('cannot be undone'), affects ALL documents, and requires explicit confirmation via confirm=true. This adds crucial behavioral context that annotations alone do not provide.

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?

Three short, front-loaded sentences. Each sentence earns its place: what happens, a critical warning, and a required condition plus an alternative. No wasted words.

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?

The description is complete for a destructive tool: it covers purpose, irreversibility, the confirmation requirement, and points to a safer alternative. Given the output schema exists, it doesn't need to explain return values. The agent has all necessary context to invoke 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?

Schema description coverage is 0%, so the description must add meaning. It explains the confirm parameter's role ('must set confirm=true to proceed'), which is essential and not obvious from the schema alone. However, it provides no additional detail about the vault parameter format, so it doesn't fully compensate.

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 clearly states the action: 'Permanently delete a vault and ALL its documents.' This is specific with a verb and resource, and it distinguishes itself from siblings by emphasizing permanent deletion and the alternative 'vault_archive'.

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?

It explicitly says 'Consider using vault_archive instead,' providing an alternative for non-permanent needs, and states the required condition 'You must set confirm=true to proceed.' It could be improved by explicitly saying when not to use, but the context is clear.

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