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

The annotations already declare destructiveHint=true, but the description adds meaningful context: the deletion is permanent and cannot be undone. It also discloses an additional side effect, namely that deleting a task cancels its pending reminder, which is valuable beyond the annotations.

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 three short sentences with no wasted text. The irreversible nature and deletion target are front-loaded, and the side effect is appended where it is most useful.

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 two-parameter destructive tool with full schema coverage and annotations, the description covers the key facts: permanence, lookup by id or exact title, and the reminder side effect. It could be slightly more complete by explicitly stating that exactly one identifier should be provided, but the core context is present.

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 100%, so both parameters are already documented by the input schema. The description reinforces that id or exact title is used, but it does not clarify edge cases such as what happens if both or neither are supplied, which matters because neither parameter is required.

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 states a specific verb and resource: permanently delete a note from the knowledge base. It also clarifies that the note can be identified by id or exact title, which distinguishes it from read/update siblings.

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 makes the delete operation clear and explains the two lookup modes, but it does not explicitly say when to use this versus kb_update_note or kb_get_note, nor does it discuss exclusions or prerequisites. Usage is implied by the destructive nature rather than explicitly guided.

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