get_pricingGet Gentoura's published Egypt, Jordan, and combined tour package prices, inclusions, exclusions, and booking process, as published at gentoura.com/pricing.md.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden. It discloses that the information is 'published' and points to a specific source URL, implying a read-only retrieval with no side effects. However, it does not describe the response format, freshness, or any caveats about the static source, leaving some behavioral ambiguity.
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?
A single front-loaded sentence that efficiently states the verb, resource, scope, and source URL. Every element is informative and there is no redundancy or filler.
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 retrieval tool, the description covers the essential selection-relevant facts: which destinations, what data categories, and the source URL. It does not specify the return format or explicitly route between siblings, but the simplicity of invocation makes this a minor gap.
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, so there are no parameter semantics to clarify beyond the schema. The description adds value by summarizing the content categories (prices, inclusions, exclusions, booking process), which exceeds the baseline for a no-parameter tool.
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 verb ('Get') and a specific resource: Gentoura's published Egypt, Jordan, and combined tour package prices, inclusions, exclusions, and booking process. It also names the source URL, which distinguishes it from siblings like get_tour and search_tours that focus on tour details and discovery rather than pricing.
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 clearly implies when to use this tool: when the agent needs published pricing, inclusions, exclusions, or the booking process for Gentoura's tours. It does not explicitly mention alternatives or exclusions, but the pricing-focused scope provides clear selection context.
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 has a distinct role: search_tours finds packages, get_tour returns full details for one package, and get_pricing provides published pricing and booking process information. There is mild overlap in that get_tour and get_pricing both include pricing, but the broader scope of each tool keeps them distinguishable.
All tool names follow a consistent verb_noun pattern: get_pricing, get_tour, search_tours. The naming is predictable and clearly indicates each tool's action and resource.
Three tools is appropriate for a focused tour-information server covering search, detail retrieval, and pricing. Each tool has a clear purpose and the small set is easy for an agent to navigate without bloat or unnecessary duplication.
The tool surface covers the core traveler journey: search tours, view specific tour details, and access pricing/booking guidance. The main gap is that booking cannot be completed through the server, but the descriptions explicitly direct travelers to the page_url for the AI concierge, so the set is complete for its informational and lead-gen purpose.