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

Annotations already declare readOnlyHint/destructiveHint=false, so the safety profile is covered. The description adds genuinely useful behavioral context beyond that: it reports whether messages have landed since the summary, and it sets an editorial rule ('never present a summary as a decision unless a sidebar settled it') that shapes how results should be interpreted.

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?

Contents are front-loaded before usage and editorial guidance, and every sentence carries weight. The opening sentence is dense with comma-separated clauses, which slightly slows parsing but remains purposeful.

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 takes on the burden of describing the return shape and does so at a conceptual level (summary, sidebars, recent messages as plain lines with speakers). It omits pagination/volume behavior, but the limit parameter in the schema partially covers that.

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%, with roomId, limit (default 40, max 200), and workspace/auth semantics all documented in the schema. The description's mention of 'most recent messages' loosely maps to limit but adds no syntax or format detail, so the 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 (a room) and enumerates exactly what is returned: a catch-up summary, sidebars with outcomes, and recent messages with speakers. It reads clearly as a read operation, but never explicitly contrasts itself with siblings like rooms_list or rooms_post, so an agent must infer the distinction.

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 concrete trigger conditions: use when a user asks what happened in a room, what a group decided, or to catch them up. There is no explicit when-not or named alternative, but the positive usage context is well specified.

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