Delete note

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

Annotations declare destructiveHint: true and readOnlyHint: false. The description adds value by emphasizing the need for explicit confirmation, which is a behavioral trait not covered by annotations. There is no contradiction.

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 efficiently conveys the tool's purpose and key requirement. However, it lacks parameter details, which slightly reduces its effectiveness.

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 two required parameters, no output schema, and annotations providing destructive context, the description is somewhat incomplete. It does not explain return values, the meaning of 'local,' or any side effects beyond deletion. It meets the minimum viable standard but has gaps.

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%, meaning the description does not explain the parameters. The description hints at the confirm parameter by stating 'after explicit confirmation,' but does not define id or specify their types or roles. This is insufficient.

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 'Delete a local note after explicit confirmation' uses a specific verb (delete) and resource (local note), clearly distinguishing it from sibling tools like create_note, list_notes, read_note, search_notes, and workspace_summary.

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 mentions 'after explicit confirmation,' providing a clear prerequisite for use. It does not explicitly state when not to use this tool or list alternatives, but the requirement for confirmation is a useful guideline.

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