Tripyana London Chauffeur

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full behavioral burden, and it discloses the single most important trait: this tool only generates a pre-filled link and never creates a booking, plus what data is embedded in the link. It does not mention return format or error/failure behavior, which keeps it from a 5, but the highest-risk behavioral fact is front and centre.

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?

Two sentences with zero waste. The core action and beneficiary ('so the traveller only picks the car and pays') are front-loaded, and the critical 'No booking is created' caveat gets its own sentence. Every word earns its place.

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?

Despite 14 parameters, the tool's behavior is simple, and the description covers the purpose, the scope of embedded data, and the non-mutating nature. The main omission is the return shape — there is no output schema and the description never states what is returned, though 'Build a link' strongly implies a URL. Slightly more would make it fully complete.

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 description coverage is 50%, so the description must partially compensate. It enumerates the parameter categories (date, time, passengers, luggage, pickup, drop-off, contact details), covering roughly 10 of 14 parameters, but adds little semantic depth beyond the schema — nothing about coordinates, note, or language interplay. It partially bridges the gap but does not fully compensate for undocumented params.

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 names a specific verb and resource ('Build a link to Tripyana's online booking form'), states what gets pre-filled (date, time, passengers, luggage, pickup, drop-off, contact details), and the 'No booking is created by this tool' clause draws a clear line against booking-creation tools. Among siblings, which are price, info, and search tools, this is unmistakably the link-builder.

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 conveys a clear use case — when a traveller should finalise car choice and payment themselves — and gives an explicit when-not ('No booking is created by this tool'). It stops short of a 5 because it never names an alternative sibling (e.g., use get_transfer_price for a quote), leaving differentiation to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the burden of behavioral disclosure. It communicates that the tool returns a read-only set of company facts and lists those facts, which is sufficient for a no-parameter information lookup. It does not detail response structure, but the enumeration partially compensates.

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 front-loaded sentence that leads with 'Company facts' and then provides a focused, semicolon-separated list of content areas. Every item earns its place, with no filler, repetition, or extraneous detail.

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 simple, no-argument, read-only company info lookup, the description is nearly complete: it names the main content categories an agent would need to decide whether this tool satisfies a request. The lack of an output schema is mitigated by the explicit enumeration of returned information areas.

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 empty schema fully defines the parameter space, so there is nothing substantive to document. The description adds useful context about what data the call returns, satisfying the baseline for no-parameter tools.

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 identifies the resource—Tripyana company facts—and enumerates the exact categories covered, including licence, contact details, policies, and service pages. This makes it easy to distinguish from the pricing, booking, and search sibling tools even without an explicit verb.

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 itemized content gives an agent clear context for when to call this tool: whenever company-level facts or general policy details are needed. It does not explicitly state 'use this instead of price/search tools,' but the boundary is obvious from the listed content and sibling names.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The description transparently notes that the result is an indicative total, not the exact booking price, and explains rules such as minimums and distance surcharges. This sets clear expectations about the tool's outputs and constraints.

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 concise sentences, front-loaded with the core pricing rules and followed by the output nature. No unnecessary words or redundant details.

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 moderate complexity (six parameters, no output schema), the description provides sufficient context to understand the tool's purpose and key constraints. It does not detail every parameter but covers the essential context for a pricing 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?

Schema descriptions cover 67% of parameters, but the tool description adds only modest clarification. It reinforces the meaning of hours and destination but leaves language and passengers unexplained. Some compensation is provided, but not enough to fully clarify all parameters.

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 what the tool does: it provides pricing for a chauffeur-driven Mercedes, covering hourly and full-day rates, with specific rules for London and outside London. This distinguishes it from sibling tools like transfer or meet-and-greet 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 implies usage for hourly chauffeur services and mentions conditions like minimum hours and distance fees, but it does not explicitly contrast with alternative tools. It lacks direct guidance on when to choose this tool over get_transfer_price or get_meet_greet_price.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations present, the description carries more weight. It does disclose that prices are fixed and lists service components, but it does not clarify return format, currency, whether the optional chauffeur transfer affects price, or any limitations. This is partial transparency but not full.

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 front-loaded sentence that states the purpose first and then provides useful parenthetical details about the service inclusions. It is compact and avoids redundancy, though slightly dense due to multiple parenthetical clauses.

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?

Without an output schema, the description should explain what the tool returns, but it only says prices are fixed. It also does not address the language parameter or clarify how the optional chauffeur transfer affects pricing. An agent would still be uncertain about the exact response and edge conditions.

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 description coverage is 67% and the description adds meaning by explaining what the vip-meet-greet and student-pickup service values refer to, including the Heathrow-specific service details. However, it adds no information about the guests or language parameters, leaving part of the semantics to the schema.

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 that the tool returns fixed prices for two specific services: Heathrow VIP Meet & Assist and student/unaccompanied-minor pickup. It is specific enough to distinguish from the sibling pricing tools by service type, but it does not explicitly contrast itself with get_transfer_price or get_hourly_price.

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?

Usage is implied by the service names and scope: Heathrow VIP Meet & Assist and student pickup at London airports. However, the description gives no explicit guidance about when to choose this tool over sibling pricing tools, and no exclusions or alternative recommendations.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the burden. The description indicates a read-only operation returning fare information and a booking page; there is no mention of side effects like making reservations or modifying data. This is transparent enough, though it does not explicitly state 'read-only'.

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, well-structured sentence that lists all key return elements (fare, recommended car, booking page) without unnecessary verbosity. It is concise and easily parsed.

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 description covers the main output (fare, recommended car, booking page) and mentions currency (GBP) and scope (airport/cruise port to central London). However, it does not specify the output format (e.g., JSON structure, list vs. object) or handle edge cases like 'no available car' or 'invalid route', but these are not required for a basic understanding.

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?

All six parameters have clear descriptions in the schema, including enumerations with examples (route), units (luggage as large suitcases), and default behavior (vehicle omitted returns all). The descriptions are unambiguous and cover the purpose of each parameter.

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 that the tool returns a fixed one-way chauffeur fare between London airports/cruise ports and central London, including recommended car and booking page. It is specific enough to distinguish from hourly or meet-and-greet pricing, though it does not explicitly contrast with those sibling tools.

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 does not explicitly state when to use this tool versus alternatives like get_hourly_price or get_meet_greet_price. It implies usage for fixed transfers, but lacks clear guidance on selection criteria, such as 'use for one-way transfers' or 'use for fixed fares only'.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the behavioral disclosure burden. It usefully reveals that the output includes fixed whole-car return prices and page links, and that the scope is private chauffeur-driven day trips. It does not clarify output structure, pagination, or whether the list is exhaustive, but for a simple catalogue tool this is acceptable.

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 one sentence but packed with useful specifics: mode of transport, destination list, pricing model, and output links. It is front-loaded with the core purpose, and the long destination list is informative rather than 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?

For a simple list tool with one optional parameter and no output schema, the description gives enough context: the catalogue's scope, contents, and that prices and links are included. It does not detail exact return fields, but the tool's simplicity and the described output content make it reasonably complete for invocation.

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 single language parameter is fully documented by the input schema with an enum and description, so the description does not need to add much. It adds no additional meaning about how the language parameter affects the catalogue, but schema coverage is complete, so the baseline of 3 applies.

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 that the tool provides a catalogue of private day trips from London, enumerating destinations and noting it includes fixed prices and page links. This makes its purpose understandable, though it lacks an explicit verb like 'lists' and does not directly contrast itself with sibling tools.

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 implies usage: an agent should call this when the user is looking for available private day trips from London. However, it gives no explicit guidance about when to prefer this over search_services or the pricing tools, and it does not mention any exclusions or alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The description indicates a read-only operation (search and return pages). No side effects or destructive actions are mentioned. Since no annotations are provided, the description carries the burden; it is reasonably transparent about being a search operation, though it doesn't address rate limits or authentication.

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 sentence that is reasonably concise. It lists many examples, which adds length but also value by clarifying the types of queries. The sentence is well-structured and front-loaded with the main action ('Search... and return matching pages').

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 search tool with three parameters and no output schema, the description provides sufficient context: it specifies what the tool searches, what it returns (pages with summary and prices), and gives example query terms. It does not detail output format or edge cases, but these are not critical for basic usage. Sibling tools add context, though the description itself is fairly complete.

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 schema covers two of three parameters (query and language) with descriptions, but limit lacks any schema description. The tool description adds value by providing example query values (e.g., 'Gatwick', 'wedding') which clarify expected input, but it does not explain the limit parameter. Overall, it adds some semantic context beyond the schema but not fully.

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: searching Tripyana's services and returning matching pages with summaries and prices. It also lists example service types and locations, which distinguishes it from sibling tools like get_transfer_price or list_day_trips that have narrower scopes.

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 implies use for general service discovery but does not explicitly contrast it with sibling tools or state when to prefer this over more specific alternatives (e.g., get_transfer_price). The examples give practical hints but lack explicit guidance on selection criteria.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.