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

Annotations already declare readOnly/idempotent/non-destructive, yet the description still adds real value: newest-first ordering, the fact that deleted messages carry null content, cursor-based paging, and a plan-tier requirement. It does not mention caps beyond what the schema shows (e.g. what happens past the last page), which keeps it off a 5.

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?

Four short, front-loaded sentences with no filler: what it reads, ordering, id provenance, read-only, field semantics, pagination, and access requirement — each sentence adds distinct information.

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?

An output schema exists, so return shape need not be described, and the definition still covers ordering, deleted-message nulls, and cursor continuation. The only gap is the undocumented limit parameter, which the schema's own default and bounds partially mitigate.

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 conversationId and cursor (via page.nextCursor) well but says nothing about limit, leaving one of three parameters undocumented outside its default/maximum constraints.

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?

Names a specific verb and resource ('Read ... direct-message conversations and its messages') plus scope ('the writer's stored'), and routes the id source to list_conversations, so it is distinguishable from its nearest sibling without opening a schema.

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?

Explicitly says to get the conversationId from list_conversations and to pass page.nextCursor as cursor for older messages, which covers the main usage path and pagination continuation. It stops short of stating when not to use it (e.g. versus list_conversations for scanning all threads), so it is clear but not fully exclusionary.

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