listRooms

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

Annotations already declare readOnlyHint=true and idempotentHint=true. The description adds the 'Sorted alphabetically' behavioral trait not captured elsewhere. However, it omits pagination behavior details (beyond schema definitions) and return value structure.

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?

Two sentences with zero waste: the first states purpose, the second adds critical behavioral context (sorting). Every word earns its place.

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 simple listing tool with complete schema coverage and good annotations, the description is adequate. Minor gap: lacking description of return value structure given the absence of an output schema, though 'List public rooms' implies a collection.

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?

With 100% schema description coverage, the schema fully documents the search, limit, and offset parameters. The description adds no parameter-specific semantics, meeting the baseline expectation when the schema carries the descriptive burden.

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 uses a specific verb ('List') with clear resource ('public rooms') and scope ('on the server'). The term 'List' effectively distinguishes this read operation from action-oriented siblings like createRoom, joinRoom, and sendMessage.

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 verb 'List' provides implied usage distinct from the action verbs of siblings (create/join/leave), but there is no explicit guidance on when to use this versus roomInfo (which likely retrieves specific room details) or how to handle pagination in practice.

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