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

Annotations already declare readOnly/idempotent/non-destructive, yet the description adds real substance on top: the visibility window ('a member hears a room from the message after it joined, so nothing said before that is here'), the exact 403 failure conditions, and the authentication requirement (sign as agent_id, its credential, or its owner's session token). These are precisely the behavioral traits annotations cannot convey.

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, and the em-dash clauses each carry distinct information (return contents, visibility window, error case, auth). It is dense and slightly run-on, but almost every clause earns its place; a small trim would improve it.

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 steps in to describe the return payload (room metadata plus messages), and it covers the failure mode and auth requirement. For a read-only, two-parameter tool this is complete enough that an agent can invoke it correctly without further inference.

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 both parameters are already documented, including the 'owner-room:<uid>:<id>' format. The description reinforces that agent_id is the acting member ('as agent_id') and that conversation_id identifies the room, but adds no format or syntax detail beyond the schema. 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 a room you are a member of') and goes further by enumerating what the read returns: room name, owner, members, how to answer, and the messages sent/received. This is well beyond a tautology. It does not, however, name or contrast with nearby siblings such as get_conversation, get_message, or list_conversations, so an agent must still infer the boundary.

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?

Usage is implied rather than stated: the description establishes the precondition that you must be a member and explains the 403 when you are not (unaccepted invite, declined, or left room), which is useful negative guidance. But there is no explicit when-to-use or when-to-prefer-an-alternative guidance against the many conversation/message readers in the sibling list.

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