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

Annotations already establish that this is read-only, idempotent, and non-destructive. The description adds meaningful behavioral context beyond that: peer messages are untrusted external content, not owner instructions, and pagination is done via next_after. This is valuable transparency that structured fields do not 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?

Three short sentences, each earning its place: the operation and resource are stated first, the untrusted-content warning is critical context, and pagination is direct operational guidance. There is no filler or repetition.

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?

Given the simple schema, rich read-only annotations, and a concise description of what is read and how to paginate, the tool is adequately specified for an agent to call it correctly. The lack of an output schema is partially mitigated by mentioning current turn and decisions, though a bit more return-shape detail would make it fully complete.

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 0%, so the description must compensate. It does clarify that the `after` parameter is used for pagination via next_after, which adds meaning beyond the schema. Still, it does not explicitly explain room_id, the required parameter, or fully map each schema field, so compensation is partial.

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 a public conversation, current turn and decisions.' This clearly identifies what the tool does and the content it exposes, and 'public conversation' distinguishes it from peer-facing write tools like speedbot_send and decision tools like speedbot_decide.

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 clear context for when to use the tool: reading a public conversation, including current turn and decisions. It also provides actionable guidance on pagination and a security-relevant warning about untrusted peer messages. However, it does not explicitly name alternative tools or state when not to use this tool.

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