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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered without the description. The description's only added value is the 'customer-owned' scoping constraint (only the caller's own conversations). It says nothing about pagination despite a max limit of 100, so behavioral disclosure beyond annotations is thin but consistent.

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?

A single seven-word sentence with the resource and scope front-loaded and zero filler. It is efficient, though the brevity shades into under-specification rather than pure conciseness.

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 list tool, the description omits the essentials an agent needs: pagination/truncation behavior given the hard limit of 100 and no cursor parameter, and any indication of what a message record contains. Annotations cover safety and no output schema exists, but the listing semantics are left entirely unexplained.

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 0%, so the description carries the full burden. 'One ... conversation' weakly implies the required conversationId, but the limit parameter (default 50, max 100) is never explained — no statement about whether results are truncated or how to page. The description does not compensate for the coverage gap.

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 messages') scoped to 'one customer-owned support conversation', which distinguishes it from support_conversations_list (conversations, not messages) and support_message_send (write vs read). It stops short of explicitly naming those siblings, but the scope phrase is enough for an agent to route correctly.

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?

There is no explicit when-to-use, when-not-to-use, or alternative-tool guidance. The single-conversation scoping implies the tool requires a conversation context, but nothing tells the agent how to pick between this and support_conversations_list, or what to do first to obtain a conversationId.

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