delete_note

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

No annotations are provided, so the description carries the full burden. It discloses the critical irreversible nature ('Permanently delete'), but does not mention side effects (e.g., broken links), permission requirements, or recovery options. The 'Permanently' is a meaningful behavioral disclosure, but more would be expected for a destructive tool.

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 a single sentence with no wasted words. It front-loads the action and scope efficiently.

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 it's a destructive tool with no annotations and no output schema, the description is sparse. It omits any mention of return behavior, error cases, or confirmations. For a simple one-parameter tool it is minimally adequate, but could benefit from noting that deletion is permanent and perhaps referencing a safer alternative.

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% for the single 'path' parameter, which is well-documented with an example and instruction to use paths from search/list. The description adds nothing beyond the schema, but that is acceptable given full coverage.

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 uses the specific verb 'delete' with the resource 'note from the vault', clearly distinguishing it from sibling tools like create_note, update_note, and get_note. The action and scope are unambiguous.

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 use when a note is no longer needed, and 'Permanently' signals irreversibility, but there is no explicit guidance on when not to use it or alternatives (e.g., moving to trash). It doesn't mention any precautions or prerequisites.

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