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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds real value beyond that: it discloses the returned content set and two explicit non-behaviors (no work assignment, no read attestation), which prevents an agent from mistaking this for an ack/claim tool. It does not explain pagination behavior or limits, keeping it from a 5.

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 return payload followed by the boundary statement, with no filler. The dense comma list is efficient, though "human decision eligibility" and "attest reads" are jargon that could be sharpened.

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 correctly carries the burden of describing return contents, and it does so. But two of three parameters, including the paging cursor, remain unexplained, and the pagination/truncation contract an agent needs to iterate is absent. Adequate but with clear gaps for a paginated read tool.

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 only 33% — just room_id is documented (with its OAuth consent note). The opaque "page" cursor (a string up to 1000 chars) and "max_bytes" (1024–16384) are undocumented in both schema and description; "paginated" hints that paging exists but gives no cursor format, defaults, or truncation semantics. With low coverage the description should compensate and does not.

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 uses a specific verb ("Returns") and enumerates the exact payload: goal, progress, changes, peer work, active claims, next steps, decision eligibility. That is far more informative than the vague title "See goal and next move." It lacks an explicit named sibling for contrast, so it stops short of a 5.

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?

Usage is only implied: the payload list suggests this is the orientation/overview call, and "Does not assign work or attest reads" pushes the agent away from mutation paths. There is no explicit "call this when..." statement and no named alternative such as catch_up or read_around for overlapping needs.

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