delete_note

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

With no annotations, the description carries full burden. It discloses security features like existence and name verification, AppleScript handling, and error messages. This adds transparency beyond the basic 'delete' operation.

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 moderately concise with structured sections for security features and output. It front-loads the primary action. Some redundancy exists in listing security features twice, but overall efficient.

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?

Given the tool's complexity (delete with verification) and the presence of an output schema (not shown but indicated), the description covers the main behavior, parameters, safety checks, and output details. Minor gaps like edge cases or prerequisites are absent but not critical.

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 descriptions like 'Primary key ID of the note to delete (e.g., 'p1308')' and 'Name of the note to verify and delete'. The description adds context about verification but does not significantly extend parameter 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 clearly states the action 'Delete a note by its primary key ID' and specifies the resource (note) and method (AppleScript verification). It distinguishes from siblings like 'delete_folder' and 'update_note' by focusing on deletion with verification.

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 when to use (when you need to delete a note) but does not explicitly state when not to use or provide alternatives from the sibling list. No guidance on prerequisites or context like ownership or permissions.

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