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

Annotations already establish this as a read-only, idempotent, closed-world call, so the bar is lower. The description still adds real value beyond them: it discloses pagination via nextCursor, warns that large pages flood the conversation, and notes the call is free. It does not warn about failure modes on a non-ready list or describe the response shape, which keeps it short of a 5.

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?

Front-loaded with the resource and pagination model, then the two practical warnings, then the alternative tool and the REST mapping. Nearly every sentence earns its place; the standalone 'Free.' fragment is terse but conveys a real cost constraint. The opening clause is dense but not padded.

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 does have to carry return-value meaning, and it partially does ('every contact detail'), plus it explains paging and the column projection. Gaps remain: it never says what a 'ready list' is, nor what response envelope accompanies the cursor. These are minor for a simple paginated read but keep it below a 5.

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 75%, so the schema carries most of the load, but the description adds actionable meaning: it ties cursor to 'nextCursor' as the paging mechanism, recommends a small limit, and advises choosing columns rather than taking the default every-column set. This goes beyond the schema's field-level definitions.

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 identifies the resource precisely — the rows of a ready list, including every contact detail — and clarifies it operates page by page. It lacks an explicit retrieval verb (phrased as a noun fragment, 'Rows of a ready list'), but an agent can still tell it fetches list rows and can distinguish it from prepare_list_file, which it explicitly names as the whole-list alternative.

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 concrete operating guidance: keep limit at 50 or less, pick columns deliberately, and use prepare_list_file when the whole list is needed. The qualifier 'ready' implies the list must be finished before this call applies, though it does not spell out what happens on a non-ready list.

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