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

Annotations already flag destructiveHint=true and idempotentHint=false, and the description adds substantial context beyond them: history/note preservation, append-to-end ordering, optimistic-concurrency refusal on revision mismatch, working-version-only mutation with readers still seeing approved versions, and privacy of private lists.

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 core action, ordering guarantee, and concurrency rule come first; the follow-up workflow and approval caveats follow in short declarative sentences. Every sentence carries distinct behavior 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?

With no output schema and a destructive, non-idempotent mutation, the description covers the prerequisites, the failure mode, the versioning semantics, and the required post-move calls. An agent has everything needed to invoke it correctly.

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 real meaning to `revision` beyond its schema text by explaining it is the source list's token from list_items and that a mismatch aborts the move. `toRevision` is left to the schema, so this is strong but not exhaustive.

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+resource with scope: moving picks between two of the person's lists, preserving note/details/history and appending in the given order. This clearly separates it from siblings like add_item, remove_item, and reorder_items without opening any 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 prerequisites and follow-ups: fetch the source `revision` from list_items, then on a live destination call review_items and confirm_items after the person's approval. It also names the escalation path (separate owner approval for publishing) and the when-not condition (revision mismatch = nothing moves).

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