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

readOnlyHint=true already tells the agent this is a safe read. The description adds value by disclosing the returned field set and the underlying REST path, but says nothing about pagination defaults or response shape beyond that, which is the main behavioral gap for a list-fetching tool.

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, front-loaded with the outcome and followed by the REST mapping. The trailing '=' in the endpoint string is slightly sloppy but costs nothing in comprehension.

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?

For a read-only, three-parameter tool with full schema coverage and no output schema, the description compensates well by naming the returned fields. Only pagination behavior is left unstated, which the schema largely covers via skip/limit.

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 skip, limit, and contact_list_id are all documented in the schema with defaults and maxima. The description only restates the endpoint and the id parameter, adding nothing beyond the schema; baseline 3 is appropriate.

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 ('Get') and resource ('one contact list including its contacts') and enumerates the returned fields, so the agent knows exactly what comes back. It doesn't explicitly contrast itself with voodoosms_list_contact_lists, but the singular 'one contact list' implies the distinction.

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?

Usage is implied: fetch a single list's contacts by id, with the id sourced from list_contact_lists. There is no explicit when-to-use/when-not statement or named alternative, so an agent must infer the routing 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.