list_waiting_rooms

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. The description only states the operation and gives no details about pagination, authentication, rate limits, what fields are returned, or whether any side effects occur. This is a minimal disclosure that adds little beyond the tool's name.

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 a single, efficient sentence with no wasted words. The action and scope are front-loaded, making it immediately scannable for an agent.

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 one-parameter list operation, the description is minimally viable. However, with no output schema and no annotations, it leaves gaps such as pagination behavior, return format, and whether any filtering beyond zone_id is supported. It also does not point to get_waiting_room for single-room retrieval.

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 100%, with zone_id already described as 'The zone ID'. The description adds only 'for a zone', which reinforces the role of the parameter but gives no additional format, constraints, or behavioral details beyond what the schema provides.

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') plus a clear resource ('waiting rooms') and scope ('for a zone'), which unambiguously identifies the action. It also distinguishes this tool from the sibling get_waiting_room, which retrieves a single waiting room rather than listing them.

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 intended usage is implied by the verb and resource — an agent can infer that this tool is for enumerating waiting rooms for a given zone. However, there is no explicit guidance on when to prefer this over get_waiting_room, no exclusions, and no mention of alternatives.

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