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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds genuine behavioral context beyond that: results come in reader order and include item ids, which is what makes the tool usable for a later mutation. It omits pagination/truncation behavior for long 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?

Two sentences, zero filler, and the purpose leads ahead of the workflow hint. Every sentence 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?

There is no output schema, but the description compensates by describing what is returned (all picks, reader order, with ids). Combined with annotations that cover the read-only profile, the definition is nearly complete; the only real gap is not clarifying its relationship to get_list_items.

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% for the single 'list' parameter, and the schema already explains it accepts an exact slug, handle/slug or id from a previous result. The description adds no further parameter meaning, so the 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?

The description states a specific verb and resource ('Read every pick in one of your lists') plus the ordering ('in reader order, with item ids'), so the operation is unambiguous. However, it never distinguishes itself from the very similar sibling get_list_items (or get_list), leaving the agent to guess which of the two near-duplicates to call.

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?

It gives an explicit when-to-use trigger: 'Call this before update_item or remove_item to get the id you need', naming the downstream tools and the reason. It stops short of stating when NOT to use it, e.g. versus get_list_items, which is a close alternative.

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