Delete Apple Notes entries by ID or exact title to clear out unwanted notes and keep your Mac organized.
Deletes a note from Apple Notes, by ID or exact title.
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "delete_note"
}
}| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v3.0.377Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of behavioral disclosure. 'Deletes' conveys a destructive action but does not state whether deletion is permanent, whether an exact title match must be unique, what happens if no matching note is found, or whether confirmation is required. These are significant omissions for a mutation 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 filler, front-loading the action and resource before the targeting details. It earns its place fully.
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?
The tool is simple in schema, but as a destructive operation with no annotations and no output schema, it should clarify permanence, ambiguity handling, and prerequisites. The discrepancy between the description's 'by ID or exact title' and the empty input schema also makes the definition incomplete for an agent trying 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?
The description claims the tool operates 'by ID or exact title,' which is meaningful parameter information. However, the input schema exposes zero properties, so there is no structured way to pass an ID or title. This mismatch leaves the agent uncertain about what arguments to actually provide and their expected formats.
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 names a precise verb ('Deletes'), a specific resource ('a note from Apple Notes'), and the accepted selection modes ('by ID or exact title'). This makes the tool's intent unmistakable and clearly distinguishes it from sibling tools like delete_reminder or gdrive_delete_file.
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 the tool should be used when a specific Apple Note needs to be removed, and it even hints at how to target it (ID or exact title). However, it provides no explicit guidance on when not to use it, no mention of listing notes first to obtain an ID, and no comparison to update_note or read_note for alternatives.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.