Get Price Estimate

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is established. The description adds useful context about the return contents (fare range, distance, duration, currency, surge multiplier), which is valuable since there is no output schema. The qualifier 'current' is slightly problematic because the input schema includes optional reserveAt for future scheduling, creating ambiguity about whether this tool handles non-current estimates.

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 no filler, front-loading the core action ('Get a current Uber fare range') and then listing the specific return fields. Every word contributes meaning, and it is appropriately sized for a read-only estimation tool.

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 inputs (two locations) and all key outputs, which is adequate for basic use. However, it does not explain the three optional parameters (riders, category, reserveAt), which could materially affect the estimate, and it does not address the reserveAt/current-time tension. For a tool with no output schema and 0% parameter description coverage, more context is needed to be considered 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 0%, and the description only hints at 'between two locations' for pickup and destination. It provides no explanation of riders, category, or reserveAt semantics, nor any compensation for the missing schema descriptions. The enum values and defaults are visible in the schema, but the tool description does not help an agent understand why or when to use these optional 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 a specific verb ('Get') and resource ('current Uber fare range') and lists concrete outputs (fare range, distance, duration, currency, surge multiplier), making the core purpose easy to grasp. However, it does not explicitly distinguish itself from similarly named siblings like estimate_ride or get_fare_breakdown, so differentiation relies on inference rather than direct comparison.

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 word 'current' and the mention of 'between two locations' imply this is for real-time fare estimates rather than historical receipts or booking. However, there is no explicit guidance about when to choose this tool over estimate_ride, get_fare_breakdown, or get_ride_options, nor any exclusions or alternative references.

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