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

Annotations already declare readOnly, idempotent, and non-destructive, so the safety profile is covered. The description adds ordering (newest first), the filter semantics (removed and not restored) and pagination behavior, which is genuinely useful, but it says nothing about result limits, permissions, or why a pick might be missing.

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?

Two sentences, zero filler, purpose front-loaded, with pagination mechanics in a short trailing sentence. Every clause (filter condition, ordering, payload, next hop) earns its place.

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, the description still discloses what comes back (notes and ids, newest first) and how to page. An agent can call this correctly and knows the ids feed restore_item; nothing essential 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 both parameters are already documented in the schema, including the accepted list identifier formats and the cursor source. The description only restates the cursor-to-nextCursor mapping, adding no syntax or format detail beyond the schema; baseline 3 applies.

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?

Specific verb (List) plus precise scope: picks removed from a list that have not been restored, in newest-first order, with notes and ids. The parenthetical reference to restore_item clearly distinguishes it from list_items, get_list_items, and the mutation tools it feeds.

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?

Implies usage clearly: the returned ids exist so they can be passed to restore_item, and the second sentence tells the agent to page with nextCursor. It lacks an explicit when-not-to-use or a contrast against sibling list tools (e.g., list_items / get_list_items), so it stops short of a 5.

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