vault_delete

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

With no annotations, the description carries full burden for behavioral disclosure. It mentions deleting and removing from all indexes but does not state whether deletion is permanent, what happens to links or references, or any error conditions. For a destructive operation, this is a significant gap.

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 concise, with one sentence for the action and one for the parameter. Every word earns its place, and it is front-loaded with the key verb and effect, avoiding any filler.

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 one-parameter delete tool, the description covers the main action and side effect. However, it does not mention the output/return behavior or possible failure modes. Given the presence of an output schema, some of this burden is reduced, but the lack of any operational context leaves room for improvement.

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 coverage is 0% and the parameter description 'path: Note path to delete' adds clear meaning beyond the schema's bare 'Path' title. Although it lacks format details, it adequately compensates for the low schema coverage by clarifying the parameter's role.

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 'Delete a note' with a specific verb and resource, and adds 'remove it from all indexes' which distinguishes it from sibling tools like vault_edit or vault_rename. This makes the tool's purpose 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 is given about when to use this tool versus alternatives. The description reads as a simple command without context for deletion versus editing or renaming, and lacks any notes on prerequisites or irreversible consequences.

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