get-rooms

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

With no annotations provided, the description carries full burden but provides minimal behavioral disclosure. It mentions 'recent' rooms which hints at temporal filtering, but doesn't explain what 'recent' means, whether results are paginated, authentication requirements, rate limits, error conditions, or what the output format looks like. For a tool with 5 parameters and no output schema, this leaves significant gaps.

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 extremely concise at just 4 words, front-loading the core purpose with zero wasted words. While it may be under-specified, it's not verbose or poorly structured.

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?

Given the tool's complexity (5 parameters including nested objects, no annotations, no output schema), the description is incomplete. It doesn't provide enough context for an agent to understand when to use it, how parameters work, what behavior to expect, or what the output contains. The minimal description fails to compensate for the lack of structured metadata.

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%, so the description must compensate but provides no parameter information. The description doesn't explain what 'limit', 'userId', 'groupIds', 'startingAfter', or the complex 'query' object do, nor how they interact with 'recent' rooms. With 5 parameters including nested objects, this leaves the agent guessing about parameter purposes and relationships.

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 verb 'Get' and resource 'Liveblocks rooms' with the qualifier 'recent', which provides a specific purpose. It distinguishes from siblings like 'get-room' (singular) by implying it returns multiple rooms, but doesn't explicitly differentiate from other list-like tools like 'get-threads' or 'get-active-users'.

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?

No guidance is provided on when to use this tool versus alternatives. The description doesn't mention when to use 'get-rooms' versus 'get-room' (singular), 'get-threads', or other retrieval tools. There's no context about prerequisites, typical use cases, or limitations beyond the implicit 'recent' scope.

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