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

Annotations already declare readOnly/openWorld, but the description adds substantial behavioral context beyond them: prices are whole-stay totals for one room, in the requested currency, charged by Nuitee as merchant of record, with Nuitee-collected taxes included and property taxes listed separately. That pricing/merchant semantics materially affects interpretation of results.

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?

Front-loaded with purpose, then result fields, then pricing semantics. Dense but each clause carries real content; the pricing/merchant paragraph is long but earns its place given there is no output 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?

With no output schema, the description fully enumerates the returned fields (id, name, stars, guest rating, coordinates, area/distance, cheapest room with total, board, refund rule, free-cancellation deadline, offer_id, and booking URLs) plus the pricing basis, leaving nothing essential ambiguous for 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 coverage is 100%, so baseline is 3. The description still adds meaning by widening 'place' beyond the schema's examples to city, region, island, airport, or landmark anywhere in the world, and by clarifying that results are capped at limit and ordered via sort (cheapest or best rated).

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?

Opens with a specific verb+resource+scope: 'Live hotel prices for a place and dates.' It is immediately distinguishable from siblings like get_hotel, list_destinations, and prebook, and it explicitly names two of them in routing roles.

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?

Routes the agent to siblings: slugs come from list_destinations, and the returned offer_id is the input for prebook. This gives clear context for when to use this tool and what to do with its output, though it never states explicit exclusions or when not to use it.

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