Price trend for a specific hotel across different check-in dates. Find the cheapest week.
| Name | Required | Description | Default |
|---|---|---|---|
| query | No | Hotel name + city | |
| weeks | No | Weeks to scan (1-6, default: 4) | |
| nights | No | Stay duration (default: 2) | |
| country | No | Country (default: us) | |
| currency | No | Currency (default: USD) | |
| start_date | No | Start date YYYY-MM-DD |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description must carry full behavioral disclosure. It mentions 'price trend' and 'cheapest week' but does not explain the data source, whether it performs live searches, what output format to expect, or any side effects. This is a significant omission for a tool with no annotation support.
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 extremely concise: two short sentences that both earn their place. The first defines the tool's core behavior, and the second states the user-facing benefit. It is front-loaded and avoids any fluff 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?
Given the tool has 6 optional parameters and no output schema, the description should explain what the tool returns and how the parameters interact. It does not describe the response format, what 'price trend' means in practice, or what happens when no parameters are provided. The description is too thin for the complexity of the 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?
The input schema has 100% parameter description coverage, so the baseline is 3. The description adds no additional meaning beyond what the schema already states; it only reinforces the idea of scanning dates and finding cheap weeks, which the schema parameters (start_date, weeks, nights) already imply.
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 purpose: showing price trends for a specific hotel across check-in dates and helping find the cheapest week. It uses a specific verb/resource combination and mentions 'specific hotel,' which helps distinguish it from sibling tools like cheapest_hotels, though it doesn't explicitly name alternatives.
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 usage is implied: use this tool when you want to see price trends or find the cheapest week for a particular hotel. However, there is no explicit guidance on when not to use it or which sibling tool to prefer instead, so the guidance is only implied, not explicit.
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.
Each tool addresses a distinct aspect of hotel research: neighborhoods, cheapest options, server health, hotel details, price trends, general search, nearby attractions, and cross-site price comparison. There is no functional overlap between tools.
Tools follow a consistent snake_case convention with descriptive names. Most are noun_noun or adjective_noun patterns (area_guide, hotel_details), with only price_compare using a verb form. The pattern is clear and predictable, though not perfectly uniform.
Eight tools cover the full spectrum of hotel information retrieval without being excessive or sparse. Each tool serves a specific, necessary function for travelers researching accommodations.
The tool set provides end-to-end coverage for hotel research: searching, filtering by price, comparing across booking sites, viewing price calendars, checking nearby places, and getting detailed reviews. There are no obvious gaps for the intended information-only use case.