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

Annotations already indicate read-only and open-world behavior. Description adds that it lists bookable rooms and links output to checkout tools. However, it does not disclose potential limits, pagination, or error conditions. With annotations covering the core safety profile, the description provides moderate added context.

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?

Three sentences, each adding value: purpose, output usage, and usage context. No redundancy or fluff. Front-loaded with the key action.

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?

Despite many parameters and no output schema, the description effectively covers the workflow context. It explains the tool's role in the broader flow (after search, before checkout). A slight gap is not addressing which parameters are required (e.g., ref is optional) or how to choose between ref, supplierCode, and supplierHotelId.

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%, so baseline is 3. Description adds value by explaining the use of ref (from search) and the relevance of supplierRoomId in subsequent tools. This contextualizes parameters beyond the schema descriptions, though not all parameters gain extra meaning.

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?

Description clearly states the tool lists bookable rooms for one hotel and date range, with a specific verb and resource. It distinguishes from sibling tools by specifying when to use (after hotel selection, before checkout) and ties the output to other tools.

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?

Explicit guidance to use hotel ref from search and call to see all rooms or refresh availability. While it doesn't state when not to use, the context is clear and implies it's for a specific hotel and date range. No explicit alternative mentioned, but siblings list other actions.

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