Deletes a note from an Obsidian vault using its file path. Use it to remove outdated or unwanted notes.
Delete a note from the vault.
| Name | Required | Description | Default |
|---|---|---|---|
| path | Yes | Path to the note to delete |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must carry the full behavioral burden. 'Delete' implies a destructive mutation, but the description doesn't state whether deletion is permanent, whether it requires confirmation, or what happens to linked references. This is a significant gap for a destructive tool with zero annotation coverage.
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?
A single, efficient sentence with no waste. It is appropriately sized for a simple tool, though it could benefit from additional routing context.
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 single-parameter deletion tool with full schema coverage, the core information is present. However, the absence of annotations, behavioral context, and sibling differentiation makes it incomplete enough to be ambiguous in a toolset with multiple delete variants.
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 100%, with the sole parameter 'path' fully documented in the schema. The description adds no parameter details beyond what the schema provides. Per the rules, when coverage is high, baseline is 3 even with no param info in the description.
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 a clear verb+resource ('Delete a note') and specifies scope ('from the vault'). However, it doesn't distinguish this from the closely named sibling 'delete_active_note', leaving ambiguity about which deletion tool to use.
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 'delete_active_note' or other deletion-related siblings. The agent receives no context about the difference between deleting a specific note by path and deleting the currently active note.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.