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

The description goes beyond the annotations by disclosing that the quote is non-binding, that it does not hold inventory or guarantee availability, and that verification steps may require keeping internal details private. These are meaningful behavioral traits beyond what readOnlyHint/openWorldHint/idempotentHint reveal. It does not contradict any annotation.

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 convey the core purpose, prerequisites, and key behavioral caveats with no filler. The most important information is front-loaded, and every clause earns its place. The density is appropriate for the tool's complexity.

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?

The description covers the main behavioral caveats and verification-handling guidance, but with 17 parameters, no output schema, and only 35% schema coverage, it is not complete enough on its own. It omits what the tool returns, how optional parameters like priceAudience or selectedRoomCount behave, and how to handle failure cases. It is adequate for tool selection but not fully sufficient 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?

The schema has only 35% parameter description coverage, so the description must compensate, but it only adds nuance for guestName/guestEmail and the travelerAssertion/agentHandoffId auth path. With 17 parameters, the description leaves required fields like propertyToken, roomId, checkIn, checkOut, and adults without any explanatory context. This is a significant gap for correct invocation.

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 outcome: 'Generate a non-binding reference quote for a traveler.' It clearly distinguishes this tool from booking-related siblings by emphasizing the quote is non-binding and does not hold inventory. The purpose is immediately understandable and not a tautology of the tool name.

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 description gives clear operational context by specifying prerequisites (guest name/email plus travelerAssertion or agentHandoffId) and notes that quotes do not hold inventory, implying this is not for provisional bookings. However, it never explicitly names an alternative tool like create_provisional_booking or states 'use this when...' versus 'use that when...'. The usage guidance is implied rather than explicit.

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