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. It discloses that deletion moves the note to 'Recently Deleted', implying soft delete behavior. This is valuable context beyond a simple 'delete'. However, it does not mention any side effects on related data or permissions required.

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 a single sentence of 7 words, containing no redundancy or unnecessary information. It is maximally concise and front-loaded with the key action and effect.

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 simplicity (one required parameter, no output schema, no nested objects), the description is nearly complete. It explains what the tool does and the main effect (soft delete). It could benefit from noting any restrictions (e.g., cannot delete notes in use), but overall it is adequate.

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 the parameter 'name' described in the schema as 'The name/title of the note to delete'. The description adds no further parameter details beyond the schema, resulting in a baseline score of 3.

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') and the resource ('note by name'), and includes the behavioral detail 'moves to Recently Deleted'. It effectively distinguishes this tool from siblings like create_note, get_note, update_note, etc.

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 indicates when to use (to delete a note), but provides no explicit guidance on when not to use, prerequisites, or alternatives. For instance, it does not mention that the deletion is reversible (soft delete) or compare to potential permanent delete options.

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