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

Annotations already declare read-only, non-destructive, closed-world behavior. The description adds valuable context beyond that: verified identity plus grant requirement, privacy scope limited to two authorized participants, observed_peer_count semantics, and the non-waking behavior of a check.

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?

The purpose is front-loaded in a single dense sentence, followed by semicolon-separated constraints. It is information-rich and has little filler, though the density makes it slightly harder to scan.

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?

There is no output schema and no schema description coverage, so the description needs to carry more of the contract. It covers auth, privacy, and one return value well, but leaves pagination parameters and most of the returned message shape 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 must compensate for all three parameters. It only hints at 'page' and does not explain conversation_id format, limit defaults/maximum, or cursor pagination semantics.

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 gives a specific verb and resource: read a page of messages in a private conversation. This is clear and distinguishable from dm_send and dm_list by implication, but it does not explicitly name or contrast with those sibling tools.

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?

It states the required identity and community:dm grant and implies use when reading private conversation messages, but it never says when to use this instead of dm_list, dm_mark_seen, or how to obtain the conversation_id. Usage guidance is present but implicit.

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