prices_digestToday's full machine-readable price digest (charter packages, tours, guides, FAQ) — same content as https://flytravel.al/llms-full.txt (cached, rebuilt hourly). Overview only; for any specific hotel/date/party use the charter_* tools.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is covered. The description adds useful behavioral context beyond annotations: the digest is cached and rebuilt hourly, and it is overview-only rather than a detailed per-hotel source.
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 a single dense sentence that front-loads the main purpose, then adds source, caching behavior, and routing guidance. Every clause earns its place; there is no filler or repetition of schema/annotation information.
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 zero-parameter, read-only, idempotent digest tool, the description is complete: it states content scope, freshness, source URL, and when not to use it. The return structure is not detailed, but the URL reference and 'machine-readable' characterization provide sufficient guidance for an agent to invoke and interpret 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 tool has zero parameters and the schema fully covers that, so there is nothing for the description to add. The baseline of 4 applies because no parameter documentation burden exists.
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 states a specific purpose: returning today's full machine-readable price digest covering charter packages, tours, guides, and FAQ. It also explicitly distinguishes this overview tool from the charter_* tools, so an agent can separate it from siblings without opening schemas.
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 gives clear routing guidance: use this for an overall digest, and use charter_* tools for any specific hotel/date/party query. This explicit when-not-to-use instruction plus named alternatives is exactly what an agent needs.
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 have clearly distinct roles, and the charter_* family is carefully delineated (cheapest by destination, cheapest by date window, filtered discovery, single hotel, comparison). There is still some surface-level overlap between charter_cheapest, charter_flexible_dates, and charter_offers, though the descriptions do enough to prevent major misselection.
The naming is generally consistent and readable: charter_* tools share a strong prefix, and hotel_details/compare_hotels/tours_list/tour_details follow predictable noun-based patterns. Minor deviations like booking_link (verb+noun) and prices_digest (noun+noun) do not create real confusion.
Twelve tools is well within the ideal range for a travel-domain server, and each tool covers a distinct query pattern: discovery, cheapest pricing, flexible dates, specific hotels, comparisons, static details, tours, and booking links. The count feels justified rather than padded.
The surface covers the main user journey well: find charters, filter by budget/features, compare hotels, get hotel details, check tours, and obtain booking links. Minor gaps exist, such as no non-charter package filtering by date/budget and no standalone flight/transfer search, but agents can still complete realistic travel-planning tasks.