list_contacts

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

No annotations are provided, so the description bears full responsibility. It states 'List contacts' which suggests a read operation, but it does not confirm read-only behavior, discuss any side effects, or mention rate limits or authentication requirements. The behavioral transparency is minimal.

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 concise (two sentences) and front-loaded with the main purpose, followed by filter details. No extraneous information, good structure.

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?

Given six parameters, no annotations, and an output schema (which the description need not explain), the description covers key filters but misses pagination behavior, sorting, or total result hints. It is adequate but not fully comprehensive.

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%, so the description adds crucial meaning by detailing status values (-1=any, 0=unconfirmed, etc.) and mentioning email, list_id, tag_id. However, it does not explain limit, offset, or other parameters like list_id and tag_id beyond naming them. Partial compensation for the missing schema descriptions.

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 'List contacts' and enumerates filter parameters (email, list_id, tag_id, status with values). This makes the purpose clear, but it does not differentiate from the sibling tool 'search_contacts' which may offer more extensive search capabilities.

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 implies usage via filter parameters but provides no explicit guidance on when to use this tool versus alternatives like 'search_contacts'. There is no mention of when not to use it or context-specific recommendations.

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