delete_user_note

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

No annotations are provided, so the description carries the full burden of disclosing behavior. It clearly states the action is deletion, but it does not mention whether the operation is irreversible, what happens if the line index does not exist, or any side effects. This lack of context is a significant gap for a destructive 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 a single, front-loaded sentence that is efficient and grammatically clear. However, given the ambiguity around the 'line' parameter, an additional clarifying sentence would have been justified.

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 delete tool with one parameter and no annotations, the description is incomplete. It does not explain how 'line' corresponds to notes listed by sibling tools like list_user_notes, nor does it mention error behavior or whether the deletion is permanent. The description is minimal and leaves the user guessing.

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 the 'line' parameter, and schema coverage is 0%. The description adds that 'line' is an index, but it does not clarify what list or note collection the index refers to, leaving the parameter meaning ambiguous.

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 uses a specific verb ('Delete') with a clear resource ('the note') and a precise scope ('at the given line index'). It distinguishes the tool from siblings like save_user_note and list_user_notes by explicitly indicating the deletion operation.

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?

Usage is implied: use this tool when you need to delete a user note identified by a line index. However, there is no explicit guidance on when not to use it or mention of alternatives such as editing via save_user_note or using run_sql for bulk deletion.

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