Look up government tourism accommodation license for a property. In Cayman Islands, unlicensed operation carries $100,000/day fine.
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | License number, property name, or address to search |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must fully disclose behavioral traits. It mentions only the tool's basic function and a legal context (Cayman Islands fine), but omits important details like authentication requirements, rate limits, or behavior when no license is found. This leaves the agent with limited behavioral understanding.
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 long, with the key action front-loaded in the first sentence. The second sentence, while providing useful context, is not strictly necessary for tool selection. Overall, it is efficient but could be trimmed without losing core purpose.
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?
The tool is simple (one parameter, no output schema), yet the description fails to explain what the tool returns (e.g., license details, owner name, status). It also leaves ambiguity about whether the tool is exclusive to Cayman Islands. Without annotations, these gaps hinder the agent's ability to interpret results.
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 100% with a single 'query' parameter described as 'License number, property name, or address to search.' The description does not add new parameter-level meaning beyond the schema; it only provides extra context about the Cayman Islands jurisdiction. Baseline of 3 is appropriate as the schema already does the heavy lifting.
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's function: 'Look up government tourism accommodation license for a property.' It uses a specific verb ('look up') and resource ('license'), and differentiates from siblings like rental_property or rental_search that handle broader property information.
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?
No explicit guidance on when to use this tool versus alternatives is provided. The description implies usage for license checks but does not specify when-not or name sibling tools as alternatives. Given the absence of such direction, the score is 3 (implied only).
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.