gorelo_list_clients

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds useful behavioral context beyond annotations by disclosing cursor pagination and the ascending client-id sort order, but it says nothing about permissions, rate limits, or what fields are returned.

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 tight sentences with zero waste. The core purpose is front-loaded, and the pagination and ordering details earn their place as non-obvious behavioral context.

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 list tool with a fully documented eight-parameter schema and a readOnly annotation, the description covers the important non-schema behavior: pagination method and sort order. It stops short of describing return fields, but no output schema exists and the schema handles filtering details, so the remaining gap is minor.

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 all eight parameters (query, cursor, pageSize, statusIds, date filters) are already documented in the schema. The description's mention of cursor pagination and sorting adds little parameter-level meaning beyond that, making 3 the appropriate baseline.

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 clients') and narrows the scope to 'the service provider.' It does not explicitly differentiate from siblings like gorelo_get_client or gorelo_list_client_locations, but the resource noun is clear enough that an agent can distinguish this as the collection endpoint.

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 as the paginated list endpoint and mentions cursor pagination, but it does not say when to prefer this over gorelo_get_client for retrieving a single client or when to use gorelo_list_client_locations. No explicit exclusions or alternatives are provided.

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