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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the safety profile is covered. The description adds real value beyond that: the shape of each row (ID, time, summary if generated, user, channel), the exclusion of message bodies, the 20-per-page cap, and the cursor/hasMore pagination contract.

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 dense sentences with no filler. Ordering and page size come first, row contents second, pagination contract last—each sentence earns its place.

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?

There is no output schema, so the description must describe return values, and it does: row fields, the conditional summary, and the pagination envelope. Combined with annotations covering safety and a fully documented schema, an agent has everything needed to call this correctly.

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 baseline is 3, but the description adds field-level meaning: it explains what mode=full yields, that default page size is 20, and how cursor/nextCursor/hasMore interact across pages. It does not explain the legacy 'page' parameter's constraint beyond what the schema already says.

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?

The description opens with a specific verb and resource ('List an agent's conversations'), states ordering ('newest first') and scope ('up to 20 per page'). It also explicitly distinguishes itself from the retrieval sibling by noting message bodies are excluded and that get_conversation returns them.

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?

It gives clear when-to-use guidance: use this for paged list rows, use get_conversation for message bodies, and use the returned nextCursor while hasMore is true. It does not explicitly contrast with other list-ish siblings such as query_conversations, export_all_conversations, or get_conversations_bulk, which is the remaining gap.

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