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

Annotations already declare readOnly/idempotent/non-destructive, so the bar is lower, and the description meaningfully adds that results are paged via hasMore/paginationToken, that totalCount is best-effort, and that attachment URLs are short-lived. These are genuine operational caveats beyond what annotations provide; it stops short of rate-limit or auth detail.

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?

The first sentence front-loads the core purpose, and the remaining clauses are dense but each carries payload (ordering, filter, paging, count caveat). No filler, though the trailing raw endpoint adds little value to an agent.

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 list tool with no output schema, the description covers what is returned, ordering, filtering, and pagination thoroughly. Missing only explicit routing guidance relative to sibling list tools, which is a minor gap.

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 the schema already documents every parameter. The description largely restates schema content (start_from = items after that time, newest_first default) and adds little new syntax or format detail, so the 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 resource and enumerates exactly what 'items' means (messages, internal notes, calls, voicemails, faxes, attachments), which is more informative than a generic 'list' verb. It reads as a plural list operation distinguishable from the singular get_conversation_item sibling, though it never names or contrasts with siblings 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 implied through the ordering and start_from filters rather than stated as when-to-use guidance. There is no indication of when to prefer this over get_conversation_item, list_conversation_scheduled_messages, or list_conversation_tags, so the agent must infer routing from the tool name alone.

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