gorelo_list_contacts

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

With no annotations, the description carries the full transparency burden, and it does disclose meaningful behavior: cursor-based pagination, a stable sort order ('sorted by contact id ascending'), and scope to the service provider. It does not describe the result envelope or any response details, but 'List' clearly signals a read-only operation.

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?

One clean, front-loaded sentence states the verb, resource, pagination, filtering, and ordering with no filler or repetition. Every clause earns its place and an agent can extract the core contract immediately.

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 tool with 10 parameters, no annotations, and no output schema, the description is informative but not fully complete. It leaves the meaning of the full-text query and multi-value filters implicit, and it does not describe the result shape, though the input schema mitigates some of this.

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?

The schema already documents 7 of 10 parameters, and the description adds only the default ordering and the client-filter intent. Parameters like query, clientIds, and statusIds lack schema descriptions and are not clarified here, so the description does not fully compensate for those gaps.

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 opens with a specific action and resource, 'List contacts', and adds concrete behavioral detail: scope ('for the service provider'), pagination mode, optional client filtering, and sort order. This makes it clearly distinguishable from siblings such as gorelo_get_contact and gorelo_list_clients without opening their schemas.

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 phrase 'optionally filtered by client' implies a common use case, and 'cursor-paginated' signals use for paging through result sets. However, the description never names alternatives or states when not to use this tool, so the usage guidance is only implicit rather than explicit.

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