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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), so the bar is lower. The description adds real value beyond them: it discloses the private-visibility scope, the room-access precondition, and the fact that reply bodies are NOT returned here.

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?

Two tight sentences, front-loaded with the primary capability before the cross-tool caveat. Dense but every clause earns its place; only the phrasing of the channel_history sentence is slightly compressed.

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?

No output schema exists, so the description compensates by enumerating the returned artifacts and flagging what is excluded (reply text). Combined with the annotations and the fully documented schema, an agent has enough to call it correctly.

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% and the two params are documented there (including the long connection-credential warning), so the schema does the heavy lifting. The description only implies that reply IDs map to a channel usable with channel_history, adding no new param syntax.

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+resource ('read one private request') and enumerates exactly what comes back: outcome, revision, delivery actions, correlated reply IDs. The 'private' qualifier and the singular 'one request' separate it cleanly from the sibling requests_list.

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 routes the agent: to get reply text, use channel_history with the recorded channel, and warns that current room access still applies. It does not state when to prefer this over requests_list or what to do if the request is inaccessible, but the alternative-tool routing is clear.

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