Delete Note

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

Adds significant context beyond the destructiveHint=true annotation: states the file is removed from disk, fails with not_found, and has no undo. It also explains the rationale for not exposing folder deletion to avoid cascading deletes. No contradiction with annotations.

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?

Two concise paragraphs: first covers deletion behavior and alternatives, second covers vault context. Information is front-loaded with the core action and no sentences are wasted, though it is slightly longer than strictly necessary.

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?

Covers failure modes, destructive nature, vault selection, and alternative for folders. Output schema presumably handles return values, so nothing critical is missing for an agent to call it correctly.

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?

With 0% schema description coverage, the description compensates by explaining vaultPath always wins over the session vault and that path refers to the note path. However, path format details and vaultPath structure are not elaborated, leaving some ambiguity for the agent.

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 the tool deletes a note from the vault, a specific verb and resource. It distinguishes itself from siblings like notes.move (for folders) and other note operations, making it clear what this tool does and does not do.

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?

Explicitly directs folder deletions to notes.move instead, and explains the vault selection mechanism (vault.current/select) with vaultPath override. This provides clear when-to-use and when-not-to-use guidance, including a concrete alternative.

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