Get available vehicle types and fare estimates for a trip. Returns a list of vehicle options with prices, ETAs, and vehicle type IDs needed for booking.
| Name | Required | Description | Default |
|---|---|---|---|
| drop_lat | Yes | Dropoff latitude | |
| drop_lng | Yes | Dropoff longitude | |
| pick_lat | Yes | Pickup latitude | |
| pick_lng | Yes | Pickup longitude | |
| drop_address | No | Dropoff address text | |
| pick_address | No | Pickup address text |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden. It explicitly states the tool 'Returns a list of vehicle options with prices, ETAs, and vehicle type IDs,' disclosing the nature of the output and implying a read-only operation. It doesn't mention side effects or limitations, but for a fare estimate tool, this is sufficient context.
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 sentences, front-loaded with the core purpose, and every word adds value. It avoids unnecessary detail and is well-structured for quick parsing.
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 there is no output schema, the description adequately explains the return value (list of options with prices, ETAs, vehicle type IDs). It covers the main purpose and even mentions the importance for booking. However, it could be more complete by noting that either addresses or coordinates can be used as input, and it lacks edge-case behavior, but it is still sufficient for a straightforward fare estimator.
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% coverage with clear descriptions for every parameter (e.g., 'Pickup latitude'), so the baseline is 3. The description does not add additional meaning about parameters beyond what the schema provides, such as the option to use addresses instead of coordinates. Therefore it neither enhances nor degrades the parameter understanding.
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: 'Get available vehicle types and fare estimates for a trip.' It specifies the resource (fare estimates and vehicle types) and the action (get), and the second sentence clarifies the return value. This distinguishes it from sibling tools like book_ride or get_route_info, which have different purposes.
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 by stating this tool returns 'vehicle type IDs needed for booking,' indicating it is a pre-booking step. However, it doesn't explicitly state when to use it versus alternatives or provide exclusions, but the context is clear enough for an agent to infer appropriate usage.
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 targets a distinct aspect of the ride-booking workflow: searching places, getting place details, estimating fares, booking, canceling, checking current ride status, viewing history, and route info. There is no overlap or ambiguity between tool purposes.
All tool names follow a consistent verb_noun snake_case pattern (e.g., book_ride, get_fare_estimate, search_places). The naming is uniform and predictable, making it easy to infer the function of each tool.
With 8 tools, the server is well-scoped for its purpose of booking rides in Africa. Each tool covers a necessary step in the user journey without redundancy or bloat, fitting comfortably in the ideal range.
The tool set covers the full ride lifecycle: search and details for locations, fare estimation, booking, canceling, current ride tracking, and history. A minor gap is the lack of ride modification (e.g., updating a destination) or payment method management, but these are not core to the primary flow.