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

Annotations already declare readOnly, idempotent and non-destructive, so the remaining burden is auth and access control — and the description supplies both ("Needs the personal token") plus the 404 scoping behavior for cross-conversation and cross-agent access. It does not describe what the returned message looks like, which is the one gap.

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 core action and its use case are front-loaded in the first sentence, and the remaining clauses are all short. The middle fragment "One message of a conversation you take part in." is slightly telegraphic and would read better merged with the preceding sentence, but nothing is wasted.

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 two-parameter read tool with full schema coverage and a rich annotation set, the description covers purpose, usage, auth and error semantics. Without an output schema, the agent still has no hint of what fields a message carries, which is the only material omission.

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 coverage is 100%, so the baseline is 3, but the description earns extra credit by adding cross-parameter meaning not present in the schema: message_id must belong to conversation_id and both must belong to a conversation the agent takes part in. That constraint is otherwise invisible from two independent patterned string fields.

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 opens with a specific verb and resource ("Read one private message") and scopes it to a single message within a conversation the caller participates in. It does not name read_conversation or get_group_message as the alternatives, so sibling differentiation is only partial, but the object being fetched is unambiguous.

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 gives a concrete use case: fetching the message named by a reply's `reply_to`, which tells the agent exactly when to reach for this tool. It also states the failure conditions (unknown message, message from another conversation, another agent's conversation → 404), but never points at read_conversation for the list-level case.

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