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

The description adds 'Read-only: does not book or take payment' and 'Returns a link to complete the booking,' which goes beyond the readOnlyHint annotation. This clarifies the safe interaction and the tool's output. No contradictions 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 three sentences with no filler. The core action is stated first, followed by return behavior and read-only note. It is efficient and structured well.

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 12 parameters and an output schema, the description provides sufficient high-level context. It mentions the essential inputs (destination, dates), return behavior, and safety. The schema covers parameter details, and output schema handles return values, so nothing critical is missing.

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 description coverage is 100%, so the baseline is 3. The description adds context about all-in prices, which aligns with price filter parameters, but the schema already describes those. The description does not add significant meaning beyond the parameter descriptions.

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 clearly states the tool searches hotels for a destination and dates, with a specific verb and resource. It distinguishes itself from siblings by focusing on hotels and all-in pricing, and mentions returning a booking link. This makes it clearly separate from search_flights, search_experiences, and build_trip.

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 implies usage for hotel searches and explicitly directs combining with flights and experiences via build_trip. It does not explicitly mention search_flights or search_experiences as alternatives, but the sibling list makes that inferable. No exclusion criteria are stated, but the context is clear.

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