Delete Note

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

Annotations mark `destructiveHint=true`, and the description elaborates on the destructive behavior: moving to recoverable trash vs permanent deletion, and the irreversible nature of reference removal. No contradictions 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?

Three sentences, each adding value. The first sentence states the main action and default behavior. The second and third cover conditional behaviors. Efficient but could be slightly more concise.

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 all key behaviors: trash vs permanent, reference handling, and the edge case where `removeReferences` is ignored when `permanent=false`. No output schema, but description suffices for agent decision-making.

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 coverage is 100% with good schema descriptions. The description adds value beyond schema by explaining that references are never rewritten when trashed, and how plain links fall back. This helps agents understand parameter interactions.

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 tool deletes a note, specifying the default behavior (move to trash) and the alternative (permanent deletion). It distinguishes itself from siblings like `move_note` (moves without deleting) and `create_note` (creates).

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 explains when to use `permanent=true` vs default trash, and when `removeReferences` is applicable. It notes that references are never rewritten for trashed files. However, it could explicitly mention alternatives like `move_note` for non-deleting moves.

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