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

With no annotations, the description carries the full behavioral disclosure burden. It states this is a read operation, specifies the data categories returned, and adds an access caveat ('current room access still applies'). It does not describe side effects or other behavioral nuances, but for a read tool the core behavior is transparent.

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 description is exactly two sentences, front-loaded with the primary purpose and followed by a useful complementary note about retrieving reply text. Every clause adds information; there is no redundancy or filler.

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 operation with no output schema, the description gives a solid picture: what data is returned, that the request is private, and how to retrieve reply text. It does not detail the output structure or error behavior, but it provides enough for an agent to invoke the tool correctly in typical workflows.

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?

The schema covers 100% of the parameters and provides rich descriptions, especially for 'connection.' The tool description adds context like 'recorded channel' and 'private request,' but it does not add meaning to the parameters beyond what the schema already provides. 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?

The description begins with a specific verb and resource: 'Read one private request.' It clarifies the scope as a single request and enumerates the associated data (outcome, revision, delivery actions, correlated reply IDs), which distinguishes it from broad listing tools like requests_list. However, it does not explicitly name or contrast sibling tools, so it lacks the strongest possible differentiation.

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?

The description gives concrete direction for using the result: 'Read reply text with channel_history using the recorded channel; current room access still applies.' It clearly implies this tool is for a single private request rather than bulk listing. It does not explicitly state when not to use it or name alternatives, so it falls short of a 5.

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