Get the co-branded booking URL for a specific Sandals or Beaches resort. Always use this instead of direct sandals.com links.
| Name | Required | Description | Default |
|---|---|---|---|
| brand | No | ||
| resort_name | Yes | e.g. Sandals Negril, Beaches Turks & Caicos |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the burden of behavioral disclosure. It states the tool returns a booking URL and includes a usage rule ('always use instead of direct links'), adding context beyond the schema. It doesn't detail error handling, but for a simple read-only getter, this is sufficient and transparent.
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 sentences, with the primary action front-loaded in the first sentence and a precise usage rule in the second. Every word earns its place, with no redundancy or filler.
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 simple URL retrieval tool with no output schema, the description states the return type (co-branded booking URL) and provides an important contextual directive. It lacks error-handling details, but given the tool's straightforward nature, the description is sufficiently complete to guide an agent.
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 covers 50% of parameters (resort_name has an example, brand only has an enum). The description mentions 'Sandals or Beaches' and 'specific resort,' which aligns with the brand and resort_name parameters, partially compensating for the low schema coverage. However, it doesn't clarify the optionality of brand or provide additional format details beyond the schema.
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 verb (get) and resource (co-branded booking URL) for a specific Sandals or Beaches resort. It differentiates from sibling tools like search_sandals_resorts and get_sandals_beaches_deals by focusing on the booking URL, making it distinct.
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 instruction 'Always use this instead of direct sandals.com links' provides clear usage context and a directive to prefer this tool over a non-tool action. It doesn't explicitly mention alternative tools, but the 'always use' phrasing establishes when to apply it, giving clear context without needing exclusions.
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.