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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false, and destructiveHint=false, so the safety profile is fully covered. The description adds real context beyond that by stating the memory is durable and versioned, which hints at concurrency semantics for later writes, but it says nothing about scope, access rules, or what an empty room returns.

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?

A single front-loaded sentence with no filler; the resource and its contents come first. The parenthetical list (decisions, conventions, state) is slightly dense but each item conveys what kind of notes live there.

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 two-parameter read with full annotation coverage and no output schema, the definition is largely sufficient: it explains what the resource contains and that entries carry versions. The only gap is return shape (key/value plus version fields) and behavior on an empty or inaccessible room, which the description neither states nor is obligated to by an output schema.

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%, so both the room slug format and the optional token override are fully documented in the schema. The description adds no additional meaning about how parameters affect the read, so the baseline of 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 gives a specific verb (read) and resource (the room's shared memory) and characterizes the payload as durable key/value notes covering decisions, conventions, and state. That is far more informative than the title alone, though it never names the write/delete siblings (room_memory_set, room_memory_delete) that an agent must distinguish when intent is to modify rather than read.

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: reading shared memory when you need durable room-level notes. There is no explicit when-to-use framing and no routing against adjacent read tools such as room_context, room_read, or room_artifacts_list, which an agent would plausibly weigh for similar information.

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