engram_load_room

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

No annotations are provided, so the description carries the full behavioral burden. The verb 'load' leaves open whether this operation mutates state, decompresses data, requires an existing room, or fails for missing rooms, and the parenthetical about 'ES-compressed closets' implies decompression behavior without confirming it.

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 padding and the core intent front-loaded; its flaw is under-specification rather than verbosity. The trailing parenthetical, however, spends words on jargon that adds no usable meaning.

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 annotations, no output schema, and 0% parameter coverage, the description is the only source of behavioral and input context — and it leaves both the 'wing' parameter and the read/mutate semantics unexplained. For a two-required-parameter tool in a dense sibling cluster, this is inadequate.

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 0% and neither parameter is described in the schema. The description alludes only to 'a specific room' and says nothing about the required 'wing' parameter or how room/wing interact, leaving half the required input undocumented anywhere.

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 supplies a verb and resource ('Return L2 context for a specific room'), but the domain jargon ('L2 context', 'ES-compressed closets for all halls') is unexplained and the parenthetical obscures rather than clarifies scope. It also does not distinguish itself from close siblings like engram_get_drawer or engram_list_rooms, so an agent cannot confidently route between them.

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 guidance on when to call this versus alternatives such as engram_get_drawer, engram_list_rooms, or engram_decompress — all plausibly overlapping. No prerequisites, no preconditions, no exclusions are stated.

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