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

The annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. Beyond that, the description adds nothing behavioral: no indication of how fresh the state is, what scope 'the room' covers, whether it is cached/aggregated, or how large the response is. Its only added signal is that the output is 'curated', which is thin.

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 short sentence with no filler and the content list front-loaded. The only cost is that the leading metaphor 'curated living memory' burns the highest-value position on an abstraction rather than on the concrete deliverable.

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 input parameters and no output schema, the description is the only source of information, and it does name the returned fields, which is the most important thing here. It still omits when to prefer it over get_decisions/search_memory and whether the state is a point-in-time snapshot or continuously updated, leaving the agent guessing about staleness.

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?

The tool takes zero parameters, so per the rubric this is the baseline 4; there is no parameter semantics for the description to clarify. It does not mislead about inputs in any way.

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 enumerates the exact contents a caller gets back (objective, status, constraints, active focus, open questions), which is a fairly specific resource definition and lets an agent distinguish it from siblings like get_decisions or search_memory. However, it is a noun phrase with no verb ('Retrieve/get'), and the framing metaphor 'curated living memory' is vague on its own; clarity comes from the parenthetical list, not the opening clause.

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?

There is no when-to-use guidance, no statement of prerequisites, and no routing to alternatives despite a crowded sibling set (get_decisions, search_memory, get_recent_messages) that likely overlaps in intent. The agent must infer that this is the high-level orientation call rather than a targeted lookup.

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