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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds real value beyond that by disclosing what a row contains and the default sort order, plus the underlying endpoint (GET /lists). It does not discuss pagination behavior or result limits, which the schema carries instead.

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 dense sentences with the payload description first, then the ordering default, then the endpoint. No redundancy or filler; every clause carries information an agent would otherwise have to guess.

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 correctly shoulders the burden of describing the return shape (id, name, counts, segments) and the default ordering. It is nearly complete for a paginated list tool, though it could mention that responses include paging metadata such as next_offset referenced in the schema.

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 limit, offset, order, and order_by are all already documented in the schema, including the next_offset paging pattern. The description's 'newest first by default' merely restates the default that order/order_by already encode, so no meaningful semantics are added beyond the 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 and resource ('List the contact lists') and enumerates the fields returned (id, name, active/unsubscribed/bounced counts, segments), which distinguishes it from a single-list fetch or a stats call. It stops short of naming siblings like get_list or get_list_stats explicitly, so the list-vs-get distinction is only implied by the verb.

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?

'Newest first by default' gives a hint about default ordering behavior but nothing about when to prefer this tool over get_list_stats or get_list_contact_counts. There are no exclusions, prerequisites, or named alternatives, leaving usage to be inferred from the tool name.

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