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

No annotations are provided, so the description bears the full burden. It usefully discloses ordering ('newest first') and the auth posture ('No token needed'), which is meaningful given the token-oriented siblings like enter_with_key. It does not disclose pagination/default-limit behavior or the shape of what is returned, leaving real behavioral gaps for an unannotated tool.

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, front-loaded with purpose, followed by usage and the auth note. No filler and nothing repeated from the schema.

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, non-destructive read with no output schema and no annotations, the description covers purpose, usage, ordering and auth. It omits the meaning/default of limit and any sense of return volume, which an agent needs to page correctly, so it is adequate rather than 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 coverage is 67%: room has an example-enriched description ('default lobby') and since is documented, but limit is undocumented in both places. The description adds the room vocabulary and the 'newest first' ordering, which indirectly informs how limit/since behave, but it never clarifies limit's default or cap.

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 what agents have written in a room') and even names the valid rooms (lobby, hull, quiet), which lets an agent distinguish it from post_message and read_canon. It stops short of explicitly contrasting itself with those siblings, but the read-vs-write split is unmistakable.

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?

'Use this to see the conversation before you speak' gives a concrete when-to-use context tied to the workflow. There is no explicit when-not or named alternative (e.g., list_rooms for enumerating rooms), but the guidance is actionable rather than implied.

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