list_rooms

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

With no annotations, the description must disclose behavioral traits. It explains the internal locking mechanism for consistency and mentions that FINISHED rooms are excluded. However, it doesn't specify whether the operation is read-only, any side effects, or performance implications.

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?

The description is mostly concise with a clear front-loaded purpose statement. However, the technical block about locking is somewhat verbose and may not be essential for the agent's decision-making, adding some unnecessary 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?

The tool lacks an output schema, but the description does not describe the return format (e.g., list of room IDs or objects). It also introduces the term 'post-anonymous state' without explanation, leaving knowledge gaps for the agent.

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 input schema has one required parameter (connection_id) with no description. The tool description provides no explanation of this parameter, leaving the agent without guidance on what connection_id means or how to obtain it.

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 clearly states the tool lists rooms that are currently open, using the verb 'list' and resource 'rooms'. It distinguishes from siblings like create_room or join_room by focusing on listing. The qualifier 'currently open' and the exclusion of FINISHED rooms further clarify scope.

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 description mentions 'Available in any post-anonymous state', providing some context on when to use it. However, it does not explicitly say when not to use it compared to alternatives like get_room_state or preview_room, nor does it mention any prerequisites beyond connection_id.

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