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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds ordering semantics, the pagination cursor field (links.next), and the underlying endpoint GET /visitors — genuinely additive. It stops short of stating page size or total-count behavior, which would be the final piece.

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, front-loaded with the resource and ordering, then pagination, then the escape hatch to the sibling. Every clause carries information the agent needs.

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 read-only paginated list with no output schema, the description compensates by enumerating the returned fields and explaining the pagination cursor. An agent can both invoke it correctly and know what to expect back without a return schema.

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?

With only one parameter and 100% schema coverage, the baseline is 3, but the description exceeds it by explaining how 'page' interacts with the response's links.next ('call again with page + 1'), which the schema alone does not convey.

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 ('List visitors (website contacts)') plus the ordering rule ('most recent chat first') and the field set returned. This clearly separates it from chaport_get_visitor (single record) and chaport_get_last_visitor_chat (conversation view).

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?

Gives explicit continuation instructions ('Use links.next in the reply for the next page (call again with page + 1)') and routes the agent to the named sibling with the selecting condition: 'To read someone's conversation, pass the visitor id to chaport_get_last_visitor_chat.' Nothing is left to inference about follow-up behavior.

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