Search Turks & Caicos rentals and island venues (restaurants, dive shops, marinas, attractions) by keyword. Returns results with id, title, and url. Then call fetch with an id for full detail.
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | Keywords, e.g. "beachfront villa", "dive shop", "italian restaurant near Grace Bay" |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Describes output shape (id, title, url) and workflow direction (call fetch for detail). No annotations exist, so description carries full burden; it adequately discloses the tool's behavior without 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?
Two clear sentences, no wasted words. Front-loaded with purpose, then output and follow-up. Perfect structure for a simple tool.
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?
Given simplicity (1 param, no output schema), the description is mostly complete: tells what it searches, what it returns, and what to do next. Lacks details on pagination, errors, but adequate for a straightforward search.
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?
Only one parameter (query) with 100% schema coverage and example in the schema. Description adds marginal value by repeating 'e.g. "beachfront villa"', but baseline 3 is appropriate since schema already provides meaning.
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 uses specific verbs and resources: 'Search Turks & Caicos rentals and island venues...by keyword'. It clearly distinguishes from siblings like 'fetch' (which retrieves full detail by id) and 'rental_search' (which likely focuses only on rentals).
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?
Tells when to use: for keyword search across multiple listing types. Explicitly instructs to 'Then call fetch with an id for full detail', providing clear next-step guidance. However, it doesn't specify when not to use or contrast with other sibling tools beyond fetch.
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.
Most tools target distinct actions, but the presence of both 'search' and 'rental_search' could cause confusion, and 'fetch' overlaps slightly with 'rental_property'. However, descriptions clarify the differences.
While most tools use a 'rental_' prefix, two tools ('fetch', 'search') lack it, and the naming style varies between verb-noun and noun-only (e.g., 'rental_availability' vs 'rental_search'). This inconsistency could confuse an agent.
With 16 tools, the set covers a comprehensive range for a Caribbean rental assistant, including search, property details, pricing, availability, licensing, market intelligence, and session management. Each tool serves a clear purpose.
The tool set covers the core lifecycle (search, view details, create sessions, add picks), but lacks session update/delete functionality. Also, 'fetch' and 'search' seem redundant with rental-focused tools. Overall, the domain is well-covered for an agent workflow.