Notes Delete Note

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

The annotations already declare destructiveHint=true and idempotentHint=false, so the agent knows the operation is destructive. However, the description itself adds no behavioral context beyond what annotations already provide, such as irreversibility, cascading effects, or permissions. It does not contradict the annotations, so it is not scored 1.

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 short, but it is shortened to the point of emptiness. It contains no functional content and is better characterized as under-specification than as useful conciseness. A concise effective description would state the delete action and target.

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?

Despite low complexity and the presence of an output schema, an agent cannot learn from the description what the tool does. The name and annotations hint at deletion, but the description itself lacks the minimal purpose statement needed to select and invoke the tool 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?

Schema description coverage is 0%, so the description needed to explain note_id and any constraints. It does not mention the parameter at all; the only clue is the schema property title 'Note Id'. The description provides zero compensatory semantic meaning.

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 is a tautology: it restates the tool name and says it is exposed through Apple-Tools-MCP. It never states that the tool deletes a note, and no operational verb or resource is described beyond the name itself.

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?

There is no guidance on when to use this tool over alternatives. Sibling tools like notes_update_note and notes_delete_folder imply related operations, but the description gives no criterion for choosing this one.

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