Search all 17 Sandals Resorts. Returns co-branded URLs (referral=135752). Use when user wants a Sandals resort.
| Name | Required | Description | Default |
|---|---|---|---|
| best_for | No | honeymoon, couples, overwater, golf, butler, first-timers, budget | |
| budget_tier | No | ||
| destination | No | Jamaica, Barbados, Saint Lucia, Bahamas, Grenada, Curaçao, Saint Vincent | |
| max_results | No | ||
| overwater_only | No |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden. It discloses a key behavioral trait by stating 'Returns co-branded URLs (referral=135752)' and scopes to all 17 resorts. However, it omits details about filtering behavior, pagination, or any potential side effects, leaving some gaps.
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 two concise sentences that front-load the action, then provide return format and usage context. Every word earns its place, with no filler or redundancy.
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 5 parameters, no output schema, and no annotations, this description is too thin. It describes the return as URLs but doesn't clarify the response structure or mention optional filters, leaving significant gaps for a search 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?
Schema coverage is only 40% (only best_for and destination have descriptions), leaving budget_tier, max_results, and overwater_only undocumented. The description does not mention any parameters or explain how they influence results, failing to compensate for the low schema coverage.
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 explicitly states 'Search all 17 Sandals Resorts,' using a specific verb ('search') and resource ('Sandals Resorts'), and distinguishes it from sibling tools like search_beaches_resorts by clearly focusing on the Sandals brand.
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 phrase 'Use when user wants a Sandals resort' provides clear, direct usage context. However, it does not mention when not to use this tool or explicitly name alternatives, just missing the exclusions part of a perfect 5.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Several tools overlap in purpose (find_cruise vs get_cruise_booking_info, and search_sandals_resorts vs get_resort_booking_url vs get_sandals_beaches_deals). However, the descriptions include explicit guidance on when to prefer each tool, which helps an agent disambiguate. Still, the catch-all request_pixie_quote overlaps with all specialized planning tools.
All tool names use lowercase snake_case with a verb-first pattern (find, get, search, plan, request). There is some inconsistency between 'find' and 'search' for similar operations, but the pattern is generally predictable.
12 tools is well within the ideal 3-15 range for a multi-product travel agency server. Each tool covers a distinct product line or function, and none feel redundant enough to remove.
The tool set covers the major travel products Pixie Vacations offers: general cruises, Virgin Voyages, river cruises, Sandals/Beaches resorts, Disney World, honeymoons, and general quote requests. There is a clear path for booking online (via URLs) or via human agent (quote form). No obvious dead ends or missing core functionality.