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

Annotations already flag this as destructive and non-idempotent-safe, but the description adds genuine behavioral context beyond them: the mandatory user-confirmation gate, the fact that without confirmed=true nothing changes and the pending change is returned for review, and the version-conflict recovery procedure.

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 tightly packed sentences, front-loaded with the destructive scope and confirmation requirement, then the sourcing and error-handling rules. No filler or redundancy.

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, confirmation-gated mutation with no output schema, the description covers everything an agent needs: what is destroyed, the confirmation requirement, how to obtain required parameters, and how to handle version mismatches. Nothing material 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 description coverage is 100%, so the schema already documents listId, confirmed, and expectedVersion thoroughly — including the confirmation semantics. The description's guidance to source values 'from the latest library_list_get' largely echoes the schema, so it stays at the baseline for a fully-covered schema.

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 (delete) and resource (Library List) with explicit scope: the entire list and all of its items. It also draws a clear boundary — 'Library Lists only, not trip checklists' — which separates it from the checklist siblings, and the 'entire...all of its items' framing distinguishes it from library_list_item_delete.

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 an explicit workflow: name the list to the user first, only pass confirmed=true after they confirm, and source listId/expectedVersion from the latest library_list_get. It also prescribes the recovery path on library_version_mismatch (re-read and reconsider, never retry blindly), leaving little to inference.

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