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

Annotations already establish readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. What the description adds is the payload shape, which matters because no output schema exists: an agent knows to expect tallies, pinned request and artifacts in a single response. It does not say anything about staleness, size or rate limits.

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 sentences, front-loaded with the value proposition and the enumerated contents, closed with the action directive. Nothing is repeated from the title and there is no 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?

With no output schema, the description carries the burden of telling the agent what comes back, and the enumeration of sections does that well. The only meaningful gap is behavioral edge cases such as what happens if the room slug is unknown or the caller is not a member.

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 both parameters (room slug, optional token override for guest follow-up) are already documented there. The description adds no format hints or guidance on the token parameter, so baseline 3 applies.

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 names a specific resource and an aggregate verb: 'Everything you need to work in a room, in one call', then enumerates the bundled sections (membership, pinned request, memory, artifacts, votes with tallies, messages, members). That enumeration implicitly separates it from the granular siblings like room_read, room_memory_get and room_artifacts_list, though none of those alternatives are named explicitly.

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?

'Call this before acting in a room' gives a clear, actionable trigger condition rather than vague suggestions. It stops short of stating when to skip it (e.g. when you already have fresh context, or when you only need one section via room_read or room_memory_get).

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