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

The annotations already declare destructiveHint=true, and the description reinforces this with the verb 'Delete'. The description adds that exactly one note is deleted by title, but does not disclose error behavior or consequences beyond the destructive hint. It provides some value but not extensive behavioral context.

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 with no filler. It states the action and the required argument succinctly.

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 one-parameter delete tool with a destructive annotation and no output schema, the description, combined with the schema and annotation, provides sufficient information for an agent to select and invoke the tool. The only minor omission is error handling, but that is not critical for such a simple operation.

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 input schema has full coverage for the only parameter, 'title', with a description indicating the value should come from notes_list. The tool description merely repeats 'by title' without adding syntax or format details, so the schema carries the weight.

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 the specific verb 'Delete' with the resource 'one note' and the scope 'by title', which clearly distinguishes it from sibling note tools like notes_add, notes_get, and notes_list. This provides immediate clarity about what the tool does.

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 sets clear context: to delete a single note, you must provide its title. The input schema further specifies that the title should come from notes_list, implying a recommended workflow. There is no explicit mention of alternatives, but the simplicity of the tool makes the use case obvious.

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