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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuine context beyond that: the sort order (latest activity first) and the fields surfaced per row (status, booker, labels), which matters since there is no output schema. It does not explain what 'did something' means operationally or how paging behaves.

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?

A single dense sentence that front-loads the verb, the scope, the ordering and the returned fields. No wasted clauses, though its compactness comes at the cost of leaving ordering/pagination detail implicit.

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 7-parameter, zero-required read tool with strong annotation coverage and a well-described schema, the description covers purpose, scope, ordering and returned fields. The remaining gap is routing guidance against get_conversation and the absence of any hint about pagination or result volume, but nothing essential for a correct call is missing.

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 86%, so all significant parameters (q, site, limit, offset, desk_id, visitor_id) are already documented in the schema. The description only echoes 'status, booker and labels' and adds no filter syntax, defaults, or interaction rules beyond what the schema provides, so 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 conversations') plus a scoping condition ('where the visitor did something') that separates it from merely browsing all visitors. It is clearly distinct from the singular get_conversation, though it never names that sibling explicitly.

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 only implied: the phrase 'where the visitor did something' hints at which conversations are included, and 'latest activity first' implies a browsing/listing use case. There is no explicit when-to-use versus get_conversation or list_visitors, and no stated exclusions or prerequisites.

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