list_contacts

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

The description discloses that results are paginated, adding some behavioral information beyond the schema. With no annotations provided, it carries the full burden but does not mention the read-only nature, default ordering, or response structure in detail.

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 description is two concise sentences, front-loaded with the main purpose and a key behavioral detail. Every word earns its place with no redundancy.

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?

The description covers the main listing behavior and pagination but lacks details about the response shape or any side effects. Given the schema documents parameters well, it is adequate but with gaps around output structure.

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?

All six parameters have descriptions in the schema, so the baseline is 3. The description summarizes search, status, and sorting parameters in plain language but adds no new semantic detail 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?

The description clearly states the tool lists contacts with optional search, filtering, and sorting, using a specific verb and resource. It distinguishes from get_contact and mutation tools, but does not explicitly differentiate from the sibling search_contacts, preventing a perfect score.

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 description provides clear context: use this tool when you need a paginated list of contacts with optional filters and sorting. It does not mention exclusions or alternatives like search_contacts, but the usage situation is evident.

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