delete_note

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

With no annotations provided, the description carries the full burden of disclosing side effects. It explicitly states that the note is moved to trash or permanently deleted depending on the app's settings, which is a key behavioral nuance beyond simply 'deletes'. This is valuable transparency, though it does not cover error handling or irreversibility in all cases.

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 concise, with two sentences and a minimal Args block. It front-loads the action, then adds the behavioral caveat, and uses no unnecessary words.

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 one-parameter delete tool, the description covers the action, the side effect (trash/permanent), and the parameter. It does not mention error behavior if the note does not exist, but given the output schema exists and the tool is simple, the description is reasonably complete.

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 input schema provides no description for note_id (0% coverage). The description compensates by explaining that note_id is 'The Joplin note id to delete', adding semantic meaning beyond the bare string type. It could include more format details, but for a single parameter this is adequate.

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 id') and the resource (note). It distinguishes from sibling tools like delete_notebook by specifying 'note' rather than 'notebook', and from update_note by clearly indicating deletion rather than modification.

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 provides no guidance on when to use this tool versus alternatives, such as when to prefer update_note or delete_notebook. It does not mention prerequisites or exclusions, leaving the usage context entirely implicit.

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