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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered; the description adds genuinely new behavior — chronological ordering (oldest first), the inclusion of triage state, and the fact that internal notes are never shown to the customer. It omits pagination/limit behavior, which matters for a message-history read.

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, tightly front-loaded with what is returned, then the usage trigger. The parenthetical enumeration of triage fields is dense but each item earns its place; there is no filler.

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?

No output schema exists, so the description carries the return-value burden, and it does so thoroughly by enumerating messages, triage state, and internal notes. Combined with annotations that cover the safety profile, an agent has enough to call this correctly; only pagination courtesy details are missing.

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 67% (limit and accountId documented, conversationId not), and the description adds no parameter-level detail — it never mentions the limit, account scoping, or where conversationId comes from. Baseline 3 is appropriate since the schema does most of the work but the description contributes nothing extra.

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 resource (one conversation's message history) and enumerates the returned data — ordered messages, triage state, internal notes — which clearly separates it from list_conversations and get_comment_thread. It lacks an explicit verb in the description body (the title supplies 'Read'), and it never names a sibling to route against, so it stops short of a 5.

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?

Gives a clear, actionable trigger: read it before replying so the answer fits the thread. However, it names no alternatives or exclusions — it does not say to use list_conversations first to obtain the conversationId, nor when this is not needed.

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