List rooms

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

With no annotations, the description carries the full burden. It states the tool lists rooms with certain details, which is basic behavior. However, it does not disclose authentication requirements, whether it returns only active rooms, or any rate limits. For a simple 0-param tool, this is adequate but not comprehensive.

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 12-word sentence that is front-loaded and contains no redundant information. 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 list tool with 0 params and no output schema, the description adequately explains the response content. However, it does not specify the return format or any potential limitations like pagination. A slightly more detailed output structure would improve completeness.

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 no parameters (0 params, baseline 4). The description adds value by specifying the output content (descriptions, photos, facilities, unpriced), compensating for the lack of parameter descriptions. Schema coverage is 100% vacuously.

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 'List' and the resource 'the property's rooms', specifying included content (descriptions, photos, facilities) and a limitation (unpriced). This uniquely distinguishes it from sibling tools like list_bookings or list_extras.

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 explicit guidance is given about when to use this tool versus alternatives. The '(unpriced)' hint suggests not using it for pricing, but no alternative tools (e.g., list_rates, search_availability) are recommended for pricing queries.

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