delete_note

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

Discloses that the operation is not permanent and is recoverable, which is critical behavioral info for a delete tool. Without annotations, the description carries the burden and does so effectively, though no details on permissions or side effects.

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?

Single sentence that is front-loaded with the action and adds key context. No unnecessary words or repetition.

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 simplicity (one param, no output schema), the description covers purpose and behavior adequately. It omits return value info, but for a straightforward action this is acceptable.

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 covers 100% of the single parameter with description 'Relative path of the note to delete'. The tool description does not add further meaning beyond that, so baseline 3 is appropriate.

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?

Description clearly states the tool moves a note to a trash folder, using specific verb 'Moves' and resource 'note to .trash folder'. It distinguishes from other operations by noting recoverability, setting it apart from potential permanent deletion.

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?

Implicitly advises using this tool for safe, recoverable deletion via the phrase 'safe delete — recoverable from Obsidian'. No explicit when-not or alternatives mentioned, but context of siblings (no permanent delete) makes it clear.

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