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

Annotations already cover readOnly/idempotent/non-destructive, and the description adds substantive behavior on top: deleted contacts excluded, page-based totals where list.memberCount equals total, canChangeVisibility meaning, createdBy 'Former member' handling, dropCount nullability, and untrusted-content wrapping. It stops short of auth requirements or ordering, and repeats the untrusted-content warning in two places.

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?

The core purpose is front-loaded, but the body is one dense paragraph that mixes return-field semantics, sibling routing, error states and a security caveat with no structure. The untrusted-content warning is stated twice, and several clauses could be trimmed without losing meaning.

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 carries the return shape: member fields, visibility, owner, createdBy, labels, projects and dropCount with its null case. An agent could call this correctly from the description alone; only ordering of members and empty-page behavior are left unstated.

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%, so page, limit and listId are already documented in the schema, making 3 the baseline. The description adds only modest value beyond that, clarifying that pagination is page-based and that list.memberCount equals total, rather than explaining limit/page interaction or defaults.

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?

Opens with a specific verb+resource: one contact list plus a page of its members, with the four returned member fields named. It implicitly distinguishes itself from the plural lnkdrp_list_contact_lists by 'One contact list' and routes to lnkdrp_list_drops/lnkdrp_tag. An explicit statement of the sibling alternative would push this to a 5.

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?

Gives real chaining guidance: a member's contactId is what lnkdrp_render_email takes (one render per member), tags come from lnkdrp_tag with listId, drops from lnkdrp_list_drops with listId. It also states the exclusion case that another person's private list returns not_found, but never says when to prefer lnkdrp_list_contact_lists instead.

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