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

Annotations already declare readOnlyHint=true, openWorldHint=false, destructiveHint=false, so the safety profile is covered. The description goes further and discloses ordering semantics (page 1 = most recent, returned oldest-to-newest) and the meaning of response fields (fromBusiness, type values, media in attachments) — real behavioral context beyond the annotations.

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 compact sentences, front-loaded with the core purpose, then ordering, then field semantics, then the ID linkage. No filler, though the field-type enumeration is dense and verges on list-like rather than prose.

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?

With no output schema, the description correctly compensates by explaining the response shape (fromBusiness flag, type enum values, attachments). Pagination limits come from the schema. It is close to complete; only the exhaustive type enumeration being duplicated inline could be trimmed.

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 100%, so all three parameters are already documented (including page default 1 = most recent). The description largely restates that and adds only the provenance of conversationId, which the schema also states. Baseline 3 is appropriate.

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 the messages in a direct message conversation') and implicitly distinguishes itself from the sibling list_conversations by explaining that the latter provides the conversationId. An agent can tell which of the two list_* tools it wants.

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 clear chaining guidance ('Use the `id` returned from list_conversations as conversationId') and explains pagination ordering, so the agent knows how to enter the call. It does not explicitly state when *not* to use this tool or name an alternative for a different need, so it stops short of 5.

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