gorelo_list_contacts

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

Annotations already declare readOnlyHint=true, so the safety profile comes from structured data. The description adds genuinely useful behavior beyond that: results are sorted by contact id ascending (oldest first) and paging is cursor-based. It does not cover result size limits, error conditions, or what a page contains.

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 sentences, zero filler, and the key operational facts (pagination style, sort order) are front-loaded. Nothing is repeated from the schema descriptions.

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 10 optional parameters and no output schema, the description is adequate on ordering and pagination but says nothing about the shape or fields of returned contacts, which the agent must infer. It is sufficient to make the call but not to interpret the response.

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%, covering query, cursor, pageSize clamping, clientIds/clientId deprecation, statusIds enum values, and date filters. The description only mentions the optional client filter, which the schema already explains, so it adds no meaning beyond it. Baseline 3 applies.

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 and resource ('Lists contacts'), plus scope ('for the service provider') and ordering. It distinguishes itself from gorelo_get_contact and gorelo_create_contact only implicitly through the verb 'list', so it stops short of 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?

Usage is implied by 'optionally filtered by client' and the pagination mention, but there is no explicit guidance on when to prefer this over gorelo_get_contact or on how to page through results versus fetching a single record. No exclusions or alternatives are named.

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