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

Annotations already establish the safety profile (readOnlyHint, idempotentHint, destructiveHint=false, openWorldHint=false). The description adds genuine behavior beyond that: results arrive newest-page-first in chronological order, and only 'visible' messages are returned, implying some content may be withheld. It does not cover error or empty-conversation behavior.

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 tightly packed sentences with no filler: purpose first, then ordering, then the two pagination cases. Every sentence earns its place and nothing is repeated from the structured fields.

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 retrieval tool with no output schema, the description covers the return shape (messages, answers, result links), ordering, and pagination cursor. The only gap is that next_before_id is referenced without stating it appears in the response payload, which an agent must infer.

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 coverage is 50% – before_id and limit carry no schema description. The description compensates for the key undocumented parameter by explaining before_id's direction and its counterpart next_before_id in the response, which is valuable given there is no output schema. limit is left unexplained, but its default and bounds are self-evident in the schema.

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 states a specific verb and resource ('Read visible messages, answers and result links in an owned agent's conversation'), which cleanly separates it from the sibling list_agent_conversations that enumerates conversations rather than messages. It stops short of naming that sibling explicitly, so the differentiation is inferred rather than stated.

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 concrete 'when' guidance for pagination: omit before_id for new replies, pass next_before_id as before_id for older history. However, it offers no guidance on when to choose this tool over alternatives, and the schema's reference to 'Conversation ID returned by these tools' leaves the discovery path (list_agent_conversations) unstated.

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