fetchFetch the full record for a result id returned by search (a hotel) or for a booking reference (prefixed 'bk_'). Returns a document with id, title, text, url, and metadata.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | An id from `search` results, or a 'bk_'-prefixed booking ref. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already provide `readOnlyHint: true` and `openWorldHint: true`, indicating a safe read operation. The description reiterates 'Fetch' which aligns with read-only behavior but adds no new behavioral context (e.g., potential side effects, rate limits, or what happens on invalid IDs).
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 entire description is a single, well-structured sentence that efficiently conveys the tool's purpose, input, and output. Every part adds value, with no wasted words.
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 low complexity (1 parameter, no output schema, rich annotations), the description is complete. It specifies input requirements, output fields, and use cases effectively, leaving no critical gaps for an AI agent to correctly invoke 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% coverage for the single parameter 'id', with description 'An id from search results, or a 'bk_'-prefixed booking ref.' The tool description adds minimal extra meaning beyond this, only reiterating the accepted formats. No additional semantics like validation constraints or examples are provided.
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: 'Fetch the full record for a result id returned by `search` (a hotel) or for a booking reference (prefixed 'bk_').' It specifies the input type and output fields, distinguishing it from sibling tools like `search` (which returns a list) and `get_booking` (which might have a different scope).
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 description explicitly tells when to use the tool: after `search` or when you have a booking reference starting with 'bk_'. However, it does not mention when not to use it or provide alternatives, leaving some ambiguity as siblings like `get_hotel_details` or `get_booking` might also apply.
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 targets a distinct action or resource, e.g., search vs search_hotels, get_booking vs get_my_booking. No overlapping functionality; descriptions clarify subtle differences.
Most tools follow verb_noun pattern (add_trip_item, cancel_booking) or get_/list_ prefixes. One outlier ('fetch') breaks the pattern slightly, but overall naming is predictable.
18 tools cover the hotel booking domain comprehensively without being excessive. Each tool has a clear role in the workflow from search to booking to modification.
Covers all key lifecycle stages: search, details, rooms, pricing, checkout (standard and one-click), booking management (list, get, cancel, modify), payment methods, and trip saving. No obvious gaps.