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

Beyond readOnlyHint=true and openWorldHint=false, it discloses a genuinely non-obvious side effect: 'Reading marks nothing as read,' which matters because a read of a conversation could plausibly create a read receipt. It also states default ordering ('oldest first'), which annotations do not cover.

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 sentences, both front-loaded with the most important facts: what is returned first, then pagination semantics, then the no-read-receipt note. The parenthetical field list is compact and useful given there is no output schema; no sentence is wasted.

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 well by enumerating returned fields, stating ordering, and clarifying the read side effect. Minor gaps remain: no mention of how many messages are returned or how before and after interact when combined.

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 three parameters are already documented, and the description's before/after wording largely restates the schema ('Return the messages after this message id'). The added value is only the intuitive threading framing, which is marginal, 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?

The description names a specific verb+resource (read one conversation) and even enumerates the returned fields (sender, author_name, body, locale, attachments), so the agent knows exactly what it gets. It does not explicitly contrast itself with the sibling list_conversations, which the agent must infer from the schema reference.

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 clearly explains how to paginate through the thread: 'before goes back in the thread, after returns newer messages,' which tells the agent when to use each parameter. It stops short of stating when to prefer this tool over list_conversations or what happens if both windowing parameters are supplied.

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