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. It does disclose the scope ('every passage on the shelf', implying an exhaustive read) and that results include links, but says nothing about whether the call is read-only, how results are ordered, or roughly how many passages come back for a name as common as Enoch.

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, and the key scoping fact ('every passage on the shelf') arrives before the result format. The 'rooms' framing is a small indirection but costs almost nothing in length.

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 one-parameter lookup with no output schema, the description covers what is selected and that links are returned. What remains unclear is the relationship to search_shelf and the rough result shape/volume, which matters for an agent deciding between the two.

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?

Coverage is 0% but the single parameter is an enum whose two values, 'enoch' and 'melchizedek', are exactly the names the description enumerates. The mapping between the parameter and the returned passage set is unambiguous from the prose alone.

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 states concretely what the tool returns: every shelf passage naming Enoch or Melchizedek, with links. The verb is implicit and the tool name 'room' is opaque on its own, but the body compensates. It does not distinguish this curated listing from the sibling search_shelf, which could plausibly do the same thing.

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 and no mention of alternatives. An agent must infer on its own whether to call this or search_shelf for topical passage retrieval, and nothing says whether the two overlap.

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