Tripyana London Chauffeur

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds the critical clarification 'No booking is created by this tool,' reinforcing its non-destructive and read-only nature beyond what annotations state. It doesn't elaborate on rate limits or authentication, but given the strong annotation coverage, the added context is sufficient for a 4.

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, efficient sentence that front-loads the primary action and includes the key disclaimer about not creating a booking. There is no redundant information, and every phrase adds value: the purpose, the filled-in details, the end-user benefit, and the non-booking clarification. This is exemplary conciseness.

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?

With 14 parameters and no output schema, the description should clarify what the tool returns (a URL string) and any special behavior. It states it 'builds a link' but does not explicitly describe the return format or how the agent should handle the link. It also omits error handling or validation notes, though all parameters are optional. Given the tool's moderate complexity and lack of output schema, the description leaves some gaps for an agent to infer.

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 has 50% description coverage, meaning many parameters lack explanations. The description lists the main categories (date, time, passengers, luggage, pickup, drop-off, contact details), which helps identify which parameters are relevant but does not add specific format, constraints, or relationships between parameters beyond what the schema already provides. It provides a high-level overview but doesn't fully compensate for the parameters without schema descriptions.

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 verb 'Build' and the resource 'link to Tripyana's online booking form' with specific details to fill in (date, time, passengers, luggage, pickup, drop-off, contact details). It distinguishes itself from booking-creation tools by explicitly noting 'No booking is created by this tool,' making its purpose unambiguous and distinct from siblings like pricing 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 when a pre-filled booking link is needed for a traveller to complete the booking, but it does not explicitly state when to use this tool versus alternatives, nor does it mention any exclusions or competing tools. There is no direct guidance on when not to use it or what alternatives exist, so while the context is implied, explicit usage direction is missing.

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 annotations already indicate this is a read-only, idempotent, non-destructive operation, which is clear. The description adds detail about the content (what facts are included) which is useful context beyond annotations. However, it doesn't disclose limitations like whether the data cache is stale or the format of the output, but given the simple nature, it's adequate.

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 efficiently lists all major content areas. It is front-loaded with 'Company facts' and then enumerates specifics. It is slightly long but each item adds value; no fluff.

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 that this is a zero-parameter, read-only tool with clear annotations and no output schema, the description is complete in scope of content. It doesn't detail response format or pagination but that's not necessary for a static info retrieval. The list of covered items is comprehensive, making it clear for an agent whether to call this or another sibling.

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?

With zero parameters, the schema is trivial. The description compensates by providing a rich list of what the tool returns, which is crucial for an agent to know if the required info is present. Thus the description provides substantial value beyond the empty 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 provides company facts and lists the specific categories (licence, number, address, etc.). The verb 'get' and resource 'company info' make it explicit. It is easily distinguished from siblings like get_transfer_price, which are about pricing for services.

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 communicates that this is a general repository for company facts and that the covered details are relevant to an agent needing background information. However, it doesn't explicitly say when NOT to use it (e.g., for specific service pricing), but the list of contents makes this implicit. It could name alternatives for pricing, but the sibling names are self-explanatory.

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?

Annotations already establish read-only, idempotent, non-destructive behavior. The description adds valuable context beyond annotations: the returned total is indicative, the booking form confirms the exact figure, and outside-London trips have extra rules. No contradiction with annotations.

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 information-dense sentences with no filler. The main product and rules are front-loaded, and the indicative-total caveat closes the description efficiently. It could be slightly tighter, but it earns each phrase.

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 price-quoting tool with six parameters and no output schema, the description covers the core scope, pricing rules, and return behavior. It does not describe every parameter, but the schema fills most gaps and the missing pieces (language, passenger count) are unlikely to cause incorrect 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?

Schema coverage is 67%, so the description partially compensates. It adds meaningful pricing semantics: 4-hour minimum in London, 8-hour minimum outside London, distance fee beyond 20 miles, and Manchester day rate. Some parameters like passengers and language are left to the schema, but those are self-explanatory.

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 resource (chauffeur-driven Mercedes in London), the pricing modes (hourly, 8-hour full-day), and the geographic scope (London and outside London). This clearly distinguishes it from sibling tools like get_transfer_price or get_meet_greet_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?

The context is clear: use this for hourly or full-day chauffeur pricing, not for transfers or meet-and-greet services. It does not explicitly name alternative tools or state when not to use it, but the scope and rules strongly imply the intended use.

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?

Annotations already declare the tool read-only, idempotent, and non-destructive. The description adds useful context about what the services include and their geographic scope, but it does not disclose return format, currency, or how the optional chauffeur transfer affects the fixed price. The incremental behavioral detail beyond annotations is moderate.

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 immediately communicates the fixed-price purpose and then packs in the service details. It is economical with no filler, though the long parenthetical makes it slightly denser than necessary.

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 package scope and location boundaries are well defined, which is adequate for a simple read-only price lookup. However, since there is no output schema, the description still leaves return format, currency, and guest-count impact unstated, and the optional chauffeur clause implies a service variation not fully explained by the parameters.

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 documents `guests` and `service`, and the description clarifies that `service` selects between the VIP meet-and-greet and student-pickup offerings, including the Heathrow vs. any London airport distinction. However, it adds no meaning for `language`, which is the one parameter without a schema description, and no detail on how `guests` influences the price.

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 very specific purpose: 'Fixed prices' for the Heathrow VIP Meet & Assist service and for student/unaccompanied-minor airport pickup. It names the exact service components and locations, making the resource unmistakable and clearly distinct from sibling pricing tools like get_hourly_price or get_transfer_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?

The description provides a clear usage context: use this tool when a fixed price is needed for the Heathrow VIP Meet & Assist package or for student/unaccompanied-minor pickup at London airports. It does not explicitly name alternative tools or exclusion cases, but the intended scope is evident.

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?

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering safety and idempotency. The description adds that the fare is fixed and all-inclusive, and that it returns the recommended car and booking page. It doesn't describe pagination, response format, or any quirks like route-specific behavior. Since annotations cover the safety profile and the description adds pricing semantics, a 3 is fair.

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 packs all key information: what it returns, pricing basis, scope, and ancillary outputs (recommended car, booking page). It's front-loaded with the core purpose and avoids redundancy. 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?

The tool is a read-only lookup with a clear scope, full parameter schema, and clear output expectations (fare, recommended car, page). It doesn't have an output schema, so the description's mention of 'recommended car and page to book' fills that gap. Missing details like currency conversion or availability are not critical for a fixed price lookup. The description is sufficiently complete for an agent to invoke correctly.

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 100%, so all 6 parameters are documented in the schema itself. The description adds context about the route type (London airports/cruise ports) and that vehicle can be omitted to get all four, but it doesn't go into parameter syntax beyond what's in the schema. With full coverage, baseline is 3, and the description modestly adds route context.

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 provides fixed one-way chauffeur fares in GBP per car, all-inclusive, for specific routes (London airport/cruise port to central London), by vehicle class, with the recommended car and booking page. The verb ('Fixed', 'get') and resource ('transfer price') are explicit, and the scope (routes, vehicle classes) differentiates it from siblings like get_hourly_price or get_meet_greet_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?

The description implies usage context: it's for fixed one-way fares between airports/cruise ports and central London. It does not explicitly state when not to use it (e.g., for hourly or meet-and-greet services), but the sibling names suggest alternatives. There's no explicit exclusion or alternative mention, but the tool's specific scope is clear enough. A 3 is appropriate because it gives context but doesn't contrast with 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?

Annotations already cover read-only, non-destructive, and idempotent behavior. The description adds meaningful context by disclosing return content: fixed whole-car return prices and page links, plus the range of included destinations. No contradiction with annotations.

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 with a long but relevant destination list. Every part contributes to telling the agent what the catalogue covers. It is somewhat dense, but not bloated or redundant beyond the title.

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 low-complexity read-only listing tool with one optional parameter and no output schema, the description sufficiently explains what is returned: trips, fixed prices, and page links. It does not discuss filtering or pagination, but none is indicated by the schema or annotations.

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 coverage is 100%, with the single optional language parameter fully documented in the schema. The description adds no additional parameter meaning, but the baseline of 3 applies because the schema already carries the burden.

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 a specific resource: a catalogue of private day trips from London by chauffeur-driven car. It names concrete destinations and states the output includes fixed prices and page links, making its purpose unmistakable and distinct from pricing or booking 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 intended use is implied: an agent should call this to browse or retrieve available day trips and their prices/links. However, the description does not explicitly say when to prefer this over search_services or other siblings, nor does it state exclusions.

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?

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, covering the safety profile. The description adds useful context about the output format (one-paragraph summary and published prices), which goes beyond the schema. It does not contradict annotations and provides additional behavioral detail that helps the agent anticipate what the tool returns.

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. It front-loads the action and resource, then provides a rich list of examples to clarify scope. Every part earns its place – no filler or repetition. It's concise and readable.

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 3 parameters, no output schema, and safety covered by annotations, the description is reasonably complete. It specifies what is returned (matching pages with summary and prices). It does not mention pagination, ordering, or the limit parameter's behavior, but these are minor given the schema. The description is sufficient for an agent to understand the tool's core purpose and output.

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% (query and language have descriptions, limit does not). The description adds no information about any parameters – it doesn't mention limit's range or meaning, nor that language restricts to en/ar. Since the limit parameter is undocumented in the schema and the description doesn't compensate, the agent lacks clarity on a key constraint. The description does not add value beyond the schema for the covered 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 the action ('Search'), the resource ('Tripyana's services'), and the return type ('matching pages with a one-paragraph summary and published prices'). The explicit list of service categories (airport transfers, cruise transfers, etc.) distinguishes it from siblings like get_transfer_price or list_day_trips, which are price-specific or list-specific. It's unambiguous what the tool does.

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?

There is no guidance on when to use this tool versus the sibling tools (e.g., get_transfer_price, get_meet_greet_price). The description implies a general search but does not state that for a specific price quote one should use a dedicated price tool, or that list_day_trips is for a full list. No explicit 'when not to use' or alternatives are mentioned, leaving the agent to infer from the tool names.

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