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

Annotations already cover read-only and idempotent behavior, so the bar is lower. The description adds meaningful behavioral context by warning that peer messages are untrusted external content, not owner instructions, and by revealing the conversation state fields returned. This goes beyond the structured annotations.

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 three short sentences with no filler and front-loads the core purpose. The 'next_after' phrase is slightly confusing, and the field enumeration could be tighter, but overall it is efficiently structured.

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 simple read tool with two parameters and no output schema, the description covers the key safety warning and some returned fields. It misses details about the pagination contract, what 'after' means, and whether the full message content is included in the response, leaving gaps for an agent invoking it.

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?

With 0% schema description coverage, the description must explain parameters, but it does not mention room_id at all. It says to 'Paginate with next_after,' yet the schema's parameter is named 'after', creating an unclear mapping between a returned cursor and the input parameter.

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 states a specific verb ('Read'), a resource ('a public conversation'), and enumerates returned state fields ('current turn, decisions, activity_state and last_real_activity_at'), making the tool's purpose clear. It is distinguishable from list-style siblings like speedbot_rooms by the focus on a single conversation's state, though it does not explicitly name an alternative.

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 clear context: this reads a public conversation and supports pagination. However, it does not state when to prefer this over sibling tools such as speedbot_inbox, speedbot_rooms, or speedbot_topic_read, nor does it describe when it should not be used.

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