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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description usefully adds the returned field set and states pagination is via limit/offset, but says nothing about total counts, ordering, or result caps beyond what the schema covers.

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?

Three short fragments, front-loaded with the resource and its returned fields, then pagination, then the endpoint. Nothing is wasted, though the bare 'GET /contacts' line contributes little to an agent that never sees the raw HTTP layer.

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 no output schema, the description compensates by naming the fields returned and explaining paging, which is the right call for a list endpoint. It stops short of noting ordering or whether a total/next_offset is returned, but the essential call-time information is present.

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% and both parameters carry their own defaults, ranges, and the next_offset chaining hint, so the schema does the heavy lifting. The description only echoes 'Page with limit and offset' and adds no format or semantics 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+resource ('List contacts') and enumerates the returned fields (name, company, job title, emails, phones, id), so the agent knows exactly what this returns. It does not, however, distinguish itself from the sibling helpwise_search_contacts, which an agent could easily confuse it with.

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?

There is no statement of when to use this versus helpwise_search_contacts, helpwise_get_contact, or filter-based alternatives. Browsing semantics are only implied by the word 'List' and the pagination note, leaving the agent to guess which sibling to pick.

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