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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint false. The description adds valuable behavioral context beyond that: ascending ID ordering, optional name-prefix filtering, and the cursor pagination mechanism with 'after'. This is genuinely useful operational detail.

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 two short sentences that convey the primary purpose and the most important pagination detail. Every word is functional, with no filler or redundant restatement of the tool name, and the critical 'next_cursor using after' instruction is included.

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 3-parameter, read-only, idempotent list endpoint with no output schema, the description is mostly complete. It gives the full resource semantics and the pagination mechanism. It could be stronger by explicitly stating what response shape includes (e.g., a next_cursor field) or by clarifying the relationship between 'limit' and pagination, but it is adequate for a correct invocation.

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. It explains 'prefix' (name prefix) and 'after' (cursor position via next_cursor), but does not explain 'limit' or its interaction with pagination. The limit parameter's constraints are visible in the schema, but its semantic role is only implied. Partial compensation, not complete.

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 and resource ('List rooms') and adds ordering semantics ('ascending ID order') and an optional filter ('name prefix'), making the tool's purpose clear. It does not explicitly distinguish itself from siblings like find_rooms or active_rooms, but the core behavior is unambiguous.

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 gives pagination usage guidance ('Follow next_cursor using after') but provides no direction on when to choose list_rooms over alternatives such as find_rooms or active_rooms. There are no explicit when/when-not or sibling differentiation statements.

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