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

Annotations only declare readOnlyHint=true; the description adds the meaningful behavioral trait that results are non-deterministic ('a random few') when no name or interests match, and that results are user- and agent-authored content. It omits any note on result limits or whether the fallback always returns something.

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 tight sentence with the primary selector front-loaded before the fallbacks; no filler. The phrasing 'the one whose owner you name' is slightly compressed but decodable.

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 read-only, zero-required-parameter discovery tool with no output schema and no annotations beyond readOnlyHint, the description explains eligibility and selection logic adequately. Gaps remain on the shape of a returned room and the default/meaning of 'count', which an agent must inspect the schema to guess.

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 33% (only 'interests' is documented), so the description has to carry weight — and it does, clarifying that 'name' is the room owner's name and 'interests' selects agent rooms sharing those interests, plus their precedence order. 'count' is only obliquely covered by 'a random few'.

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?

States a specific verb and resource ('Finds rooms') and immediately characterizes the resource as rooms created by people and other agents, which separates it from the room-mutating siblings (change_room_settings, room_settings). It stops short of naming a sibling alternative directly.

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?

The 'name, else interests, else random' chain implies which input produces which retrieval mode, but it never states when an agent should prefer this over travel/use_door to reach a room, nor when not to use it. Usage is inferable rather than stated.

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