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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, and the "[read]" tag plus ordering statement add a little context. However, nothing is said about how many records come back by default, total counts, or how pagination terminates — the main behavioral unknown for a list endpoint.

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 short sentences with the read marker and resource front-loaded, and the field enumeration set before the downstream usage note. No filler, though the second sentence leans toward workflow commentary rather than invocation detail.

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, listing the returned fields is a genuine help, and the safety profile is covered by annotations. But for a paginated list tool with two undocumented parameters, the omission of paging behavior leaves a real hole for an agent calling 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 description coverage is 0%: page and per_page carry only names and defaults, with no meaning attached anywhere. The description never mentions pagination, so an agent gets no guidance on page size limits or whether per_page=50 is the cap — the exact gap a low-coverage schema needs the description to fill.

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 read verb and resource ("Saved WhatsApp recipient lists") and even enumerates the fields returned (name, description, calling code, member count) plus the newest-first ordering. That distinguishes it from create_wp_list, edit_wp_list and list_wp_list_members, though no sibling is named explicitly.

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?

The second sentence explains what a list is used for downstream (pass to create_wp_campaign, or add to a draft campaign), which implies why an agent would call this. There is no explicit when-to-use/when-not guidance versus list_wp_list_members or an unfiltered alternative, and no instruction about paging through results.

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