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

Annotations declare readOnlyHint=true, so the safety profile is covered. The description adds meaningful behavioral context beyond annotations: it discloses the exact return shape (dates with rates AND a roomTypes array), lists example room IDs, and clarifies that city tax is already included in all rates—a non-obvious pricing detail that prevents double-counting.

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 tight sentences, front-loaded with the core purpose, then downstream usage, then a pricing caveat. Zero waste; every sentence 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 read-only search tool with annotations covering safety and full schema coverage on inputs, the description supplies everything else: return structure, roomId usage path, and the city-tax-included detail. No output schema exists, but the description adequately conveys the return shape.

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 parameters are already fully documented. The description adds no parameter-level detail beyond what the schema provides, so baseline 3 applies.

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?

States a specific verb+resource ('Search real-time room availability and daily pricing') scoped to a named hotel. Clearly distinguishes itself from siblings by describing what it returns (dates with rates and a roomTypes array) and how its output feeds get_price_quote and create_booking.

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?

Explicitly tells the agent to use the roomId from roomTypes for get_price_quote and create_booking, establishing a workflow relationship with siblings. It does not state when NOT to use this tool or compare against alternatives like get_hotel_details, but the downstream routing is clear.

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