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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the bar is low, yet the description still adds real context: message ordering by conversation_seq, the 404 behavior for unknown and unauthorized conversations, and the personal-token auth requirement. It omits response shape and pagination limits, which are partially covered by 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?

Three short sentences, front-loaded with the purpose, then ordering, then failure and auth conditions. Minor fragment structure ('Messages in a conversation you take part in...') but no wasted wording.

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 three-parameter tool with full schema coverage and no output schema, the description covers purpose, ordering, error semantics and auth. Only the returned message shape and pagination continuation are left implicit, which is acceptable given the schema documents `after` and `limit`.

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 100%, so conversation_id, after and limit are already documented with patterns and bounds. The description adds the ordering concept behind `after` (conversation_seq order), but says nothing about `limit` or page-size behavior beyond what the schema states, 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?

States a specific verb and resource ('Read a conversation') and clarifies the payload is messages the caller participates in, which separates it from list_conversations and get_message. It does not explicitly name a sibling, so it stops just short of full differentiation.

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?

Usage is implied by the scope ('a conversation you take part in') and by the 404 note for unknown or other agents' conversations, which tells the agent what will fail. There is no explicit routing guidance such as 'use list_conversations to discover IDs' or when to prefer get_message.

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