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

Annotations already declare read-only, idempotent, non-destructive behavior, so the bar is lower. The description adds real value beyond that by disclosing the ordering (newest page first) and the composition of returned posts, including internal whispers and resolve/transfer events, which an agent could not infer from the schema.

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 dense sentences with zero filler; the core purpose and the ordering constraint are front-loaded, and the paging alternatives and endpoint follow compactly.

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 describing what the returned posts contain and how they are ordered. Pagination modes are covered; only the choice against sibling retrieval tools is absent, which is a minor gap for a well-specified read tool.

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 all five parameters are already documented in the schema. The description adds only that before_uuid/after_uuid are post uuids and that the two paging styles are alternatives, which is marginal beyond the schema's 'exclusive' notes.

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 (Retrieve) and resource (one conversation and its posts), enumerates what posts include (messages in/out, internal whispers, resolve/transfer events), and notes ordering (newest page first). It is clearly distinguishable from siblings like list_conversations and get_conversation_by_phone.

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?

The description explains how to page (page/page_size or before_uuid/after_uuid), which is useful invocation guidance, but it never states when to choose this tool over list_conversations or get_conversation_by_phone. Usage context is implied by 'one conversation' rather than made explicit.

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