obsidian_delete_note

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

With no annotations, the description carries the full burden, and it does disclose two real behavioral traits: default destination is the vault trash (a recoverable soft delete) and a revision check guards the operation. However, it omits what happens on a revision mismatch, that permanent deletion is likely irreversible, and any 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?

A single front-loaded sentence with no padding. The phrasing 'Deletes or moves a note to the vault trash' is slightly muddy since trash-as-destination already implies a move, but it wastes no 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?

A destructive tool with no annotations, no output schema, and 0% schema description coverage needs more than one clause. Missing irreversibility semantics, error behavior on revision mismatch, and confirmation requirements leave the agent under-informed before an irreversible-feeling operation.

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 compensate, and it only partly does. 'Revision check' clearly maps to expectedRevision and 'trash' implies the permanent flag's default, but the critical meaning of permanent (bypass the trash / irreversible) and the path format are never explained.

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?

States a specific verb (deletes) plus resource (note) and adds meaningful scope detail: trash destination and a revision check. The only ambiguity is versus the sibling obsidian_move_note, since 'moves a note to the vault trash' overlaps lexically with a move operation, but the delete framing distinguishes it adequately.

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 when-to-use guidance, no prerequisites, and no mention of alternatives. An agent cannot tell from this text when deletion is appropriate versus obsidian_move_note for relocation or obsidian_update_note for content changes.

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