get_quote

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

With no annotations, the description carries the full burden of behavioral disclosure. It reveals that the tool returns prices for all vehicles and that it should be called before booking, which are key behavioral traits. While it doesn't explicitly state it has no side effects, the verb 'calculate' and the name 'get_quote' strongly imply a non-destructive read operation.

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 three short sentences, each serving a distinct purpose: stating the action, describing the output, and providing usage guidance. It is front-loaded with the most important information and contains 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 description provides the essential context: it returns prices for all vehicles and is a prerequisite for booking. It does not address edge cases or conditional parameter requirements (e.g., num_hours for hourly bookings), but the schema already covers those details, making the description reasonably complete for a simple quote 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 schema has 100% description coverage, so the baseline is 3. The description adds no additional parameter-level detail beyond what the schema already provides, so it does not exceed the baseline.

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 calculates the exact price for a private chauffeur transfer and returns prices for all available vehicles. It distinguishes itself from the sibling tool book_ride by positioning this as a pre-booking step, and the mention of 'prices' differentiates it from get_vehicles.

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 explicitly instructs to call this tool before book_ride, providing a clear usage order and alternative. This directly addresses when to use the tool versus a key sibling, fulfilling the requirement for explicit usage guidance.

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