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

Annotations already declare destructiveHint=true and idempotentHint=true, but the description goes further: it emphasizes permanence, explains the confirmed=true gate (without it the tool changes nothing), and prescribes recovery on library_version_mismatch ('read the list again... never retry blindly'). This is exactly the behavioral context annotations cannot carry.

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?

Five short sentences, action front-loaded, followed by confirmation workflow, value sourcing, and error recovery. Every sentence carries distinct operational value with no filler.

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 destructive, version-guarded mutation with no output schema, the description covers the confirmation gate, parameter provenance, and version-conflict handling. Nothing an agent needs to invoke it safely is missing.

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 coverage is 100%, so the baseline is 3, but the description adds sourcing semantics beyond the schema by telling the agent to pull listId and expectedVersion 'from the latest library_list_get.' It does not add format or edge-case meaning for itemId, so it sits just above baseline.

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?

States a specific verb and resource ('Permanently delete one item from an owned Library List') and explicitly bounds scope with 'Library Lists only, not trip checklists,' which separates it from the checklist_items_remove sibling. An agent can identify the operation and its object without opening the schema.

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?

Gives explicit sequencing ('Show the user the exact item first; call with confirmed=true only after they confirm'), names the source tools for the required values (library_list_get), and states the exclusion ('not trip checklists'). When-to-use, prerequisites, and the alternative boundary are all present.

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