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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds ordering and pagination behavior ('newest page last', backwards paging) plus 'Messages are permanent', which reassures that nothing is consumed or mutated. It omits the page-size default behavior, whether ordering is strictly ascending, and any retrieval limits.

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 core action and followed by the paging hint. 'Messages are permanent' is terse but does earn its place as a non-mutation cue; the ordering phrase 'newest page last' is slightly ambiguous for the space it takes.

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?

This is a small three-parameter read tool with an output schema already documenting return values and annotations covering safety. The description covers purpose, ordering, and the paging cursor, which is enough for correct invocation; only the limit default is unaddressed and that is visible in the schema.

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 must carry parameter meaning. It explains before_seq as the backwards-paging cursor and implies conv_key via 'in a conversation', but never mentions the limit parameter or its default of 50, leaving a third of the parameters undefined in both schema and prose.

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 messages in a conversation'), which cleanly separates it from write-side siblings such as send_message and from list_conversations. It does not explicitly name an alternative, so it stops short of full sibling 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?

Gives one concrete usage instruction, 'Pass before_seq to page backwards through history,' which tells the agent how to traverse history. It offers no guidance on when to choose this over list_conversations, read_entries, or get_message_receipts, and no exclusion conditions.

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