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

Beyond the readOnly/openWorld/non-destructive annotations, the description discloses rich behavioral context: the guest pays the hotel directly, displayed totals include taxes and an itemized 1Stay Booking Fee, loyalty points are eligible, and non-refundable rates cannot be changed or canceled. It also clarifies domain terminology (run of house, select-service suites) that materially affects how the agent should interpret results. No contradiction with annotations.

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 front-loaded with the core purpose in sentence one and organized into three coherent blocks: purpose/outputs, payment/pricing behavior, and room-type terminology. It is longer than average, and the room-type notes are somewhat educational, but every sentence adds operational value and nothing is redundant with the schema.

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?

Given that an output schema exists, annotations cover the safety profile, and the input schema documents all six parameters at 100% coverage, the description fully covers the remaining gap: purpose, pricing behavior, fee disclosure, loyalty eligibility, and rate semantics. The only minor omission is an explicit call sequence (search first, then detail, then book), but the book_hotel linkage makes this inferable.

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 100%, so the baseline of 3 applies. The description reinforces the 'exactly one room' constraint that matches the rooms const=1 schema, but it does not add new parameter-level semantics beyond what the schema already documents.

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 opens with a specific verb and resource: 'Get rates and room details for exactly one room at a specific hotel.' It enumerates concrete return values (room types, live rates, amenities, cancellation policies, rate_codes) and even ties rate_codes to the book_hotel sibling, which clearly separates it from the search_hotels sibling.

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 scope language ('exactly one room at a specific hotel') and the mention of 'rate_codes required by book_hotel' make the intended flow clear: query details for an already-identified hotel, then use the result to book. However, no sibling is named explicitly and there is no explicit when-not-to-use statement, so the routing to alternatives is implied rather than stated.

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