delete_note

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

The description explicitly states that deletion moves the note to Joplin's trash rather than permanently deleting it. This is a key behavioral disclosure beyond the parameter schema. No annotations are provided, so the description carries full responsibility for transparency.

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: two sentences that front-load the core action ('Delete a note by its id') and then add a crucial nuance (trash vs. permanent delete). No superfluous 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 tool with one parameter, the description is mostly sufficient. However, given the presence of sibling tools like 'complete_todo' and 'update_note', it lacks guidance for choosing this tool over those. It also does not explain the return value, but an output schema exists.

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%, but the description merely says 'by its id', which adds no insight beyond the parameter name. It does not explain what a valid note_id looks like, how to obtain one, or any constraints.

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?

Description clearly states the verb 'delete' and the resource 'note by its id'. This distinguishes it from sibling tools like 'create_note', 'update_note', and 'get_note', which have different purposes.

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?

No guidance on when to use this tool versus alternatives like 'complete_todo' for todo notes or 'update_note' for modifications. The description only mentions trash behavior, which is a behavioral trait, not a usage criterion.

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