delete_note

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

The description includes a destructive warning and the HTTP method, adding value beyond the annotations which already mark destructiveHint=true. It also explicitly requires user confirmation.

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 somewhat redundant with repeated phrases like 'Delete a note' and 'Deletes a record.' The banner-style first line could be integrated more concisely.

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 single-parameter destructive tool, the coverage is adequate: it states the purpose, the HTTP method, and the need for user confirmation. It could mention idempotency but that is already in annotations.

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?

All parameters (id only) are fully documented in the input schema. The description adds no extra information about the parameter beyond what the schema provides.

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 explicitly states it deletes a note. However, with sibling tools like 'delete_a_note' also present, it does not differentiate itself beyond the entity type 'note'.

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?

It advises confirming with the user before calling, but lacks guidance on when not to use or alternatives (e.g., other delete tools or soft-delete options).

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