Find lodging & booking link

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

The description discloses key behavioral traits beyond annotations: it prebooks and holds a rate, never charges, attributes booking, returns checkout URL for payment on LUXSKI, and requires OAuth. No annotation contradictions.

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, front-loaded main purpose. Some redundancy (OAuth mentioned twice implicitly), but efficient overall. Could be slightly more structured.

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?

Covers modes, auth, and payment handling. Output schema exists (not shown) so missing return details are acceptable. No mention of error cases or rate limits, but adequate for a booking tool.

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?

With 100% schema coverage, baseline is 3. The description adds value by explaining how hotelName and dates together trigger prebooking vs availability, and clarifies powderEventId for attribution.

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 does lodging near a resort via LUXSKI. It differentiates two modes: prebooking with hotelName+dates (returns checkout URL) and availability-only without (returns availability+booking link). This distinguishes it from siblings like plan_ski_trip or get_destination.

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 explains when to use each mode (with hotelName+dates vs without) and notes the OAuth requirement. It doesn't explicitly exclude alternative tools, but given no other lodging booking tools among siblings, this is sufficient.

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