obsidian_delete_note

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

With no annotations, the description must disclose behavioral traits. It states the note is deleted and returns a success message or error, but omits critical details such as whether deletion is permanent or reversible (e.g., moved to trash), effects on links, or permission requirements.

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 appropriately short and uses a clear Args/Returns structure, front-loading the purpose. It could be slightly more concise, but overall efficient.

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?

Given the tool's simplicity and two required parameters, the description lacks context on error handling (e.g., what if note doesn't exist), side effects, and does not explain the output beyond 'Success message or error', despite an output schema existing.

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%. The description simply lists parameter names ('vault', 'path') without adding any semantics, examples, formats, or constraints beyond the schema.

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 ('Delete a note') and the resource ('from the vault'), distinguishing it from sibling tools like 'obsidian_create_note' or 'obsidian_move_note'.

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?

The description implies usage for deletion, but lacks explicit guidance on when to use versus alternatives, prerequisites (e.g., note must exist), or when not to use (e.g., if the note has backlinks).

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