delete_note

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

The description discloses that the operation is not a permanent delete but a move to trash, adding meaningful context beyond the destructiveHint annotation. It also restricts the operation to Markdown notes, clarifying scope. It does not mention details like whether the trash folder is auto-created or if the operation can be undone, but the core behavior is well conveyed.

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 sentence of about a dozen words that front-loads the action and includes no filler. Very efficient and well-structured.

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?

For a simple two-parameter tool with no output schema and an annotation flagging it as destructive, the description covers the essential behavior and clarifies the trash semantics. It could mention parameter formats or error cases, but it is largely sufficient for correct invocation.

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?

The schema has no descriptions for the vault and path parameters, and the tool description does not explain them either. While the names are self-explanatory, the description adds no explicit parameter guidance and thus fails to compensate for the 0% schema 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 clearly states the tool moves a Markdown note to the vault trash, a specific action that distinguishes it from a permanent delete and from the sibling move_note tool. The verb 'Move' and the resource 'Markdown note' make the purpose 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 phrase 'instead of permanently deleting it' implies this tool is for reversible deletion, giving clear context for when to use it. However, it does not explicitly name alternative tools or state when not to use it, so it stops short of full guidance.

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