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.