delete_note

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

With no annotations provided, the description carries full responsibility for behavioral disclosure. It adds 'permanently,' indicating irreversibility, which is valuable, but it omits important details like error handling, idempotency, auth requirements, and side effects. The output schema exists but is not referenced, so the description only minimally covers the behavioral profile.

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 extremely concise: one opening sentence and a one-line argument explanation. Information is front-loaded, with no wasted words or redundancy.

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 single-parameter delete tool, the description covers the core operation and parameter provenance. However, with no annotations, it lacks details about edge cases (e.g., non-existent note, permissions) and doesn't mention what the response contains (though an output schema exists). It's adequate but not thorough.

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 provides no description for note_id (0% coverage), so the description must compensate. It does so by explaining the note_id is 'as returned by list_notes or search_notes,' giving the agent a clear source for a valid value. This adds meaningful context beyond the schema's bare title.

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 states the exact action: 'Delete a note permanently.' This is a specific verb (delete), resource (note), and qualifier (permanently), which clearly distinguishes it from siblings like add_note, list_notes, search_notes, and get_note.

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 implicitly guides usage by stating the note_id must come from 'list_notes or search_notes,' providing a clear prerequisite. While it doesn't explicitly mention alternatives or when-not-to-use, the context is clear enough for a straightforward delete operation.

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