delete_noteDelete a single note by ID, moving it to Recently Deleted for 30-day recovery. Requires human confirmation before deletion.
Delete one note by id. Notes.app moves it to Recently Deleted, where it stays recoverable for 30 days — this never permanently destroys it. There is no batch or title-based variant.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Id of the note to delete. |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The annotations already mark destructiveHint=true, but the description adds important nuance: the note moves to Recently Deleted, stays recoverable for 30 days, and is never permanently destroyed. This materially changes how an agent should weigh invoking the 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?
Two tight, front-loaded sentences communicate scope, side effects, recovery behavior, and boundary conditions without wasted words. Every clause earns its place.
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 one-parameter delete tool, the description covers what it does, how to invoke it, what happens to the data, and what variants do not exist. The lack of an output schema is acceptable here because the behavioral outcome is fully described.
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%, so the schema already documents the single 'id' parameter fully. The description confirms 'by id' but adds no extra format, source, or lifecycle detail beyond the schema.
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?
States a specific action ('Delete one note by id') with a clear resource and scope. The 'no batch or title-based variant' line also distinguishes it from any broader deletion sibling and from note-search/lookup tools.
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 frames usage as deleting a single note by id and gives a negative constraint: there is no batch or title-based variant. This tells an agent when to use this tool and when not to reach for a non-existent alternative.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.