Get ride quotes

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

Annotations already declare readOnlyHint=true, so safety is covered; the description adds genuinely new behavior beyond that — non-booking semantics and a 5-minute expiry that forces re-quoting. It stops short of describing result shape or how many services typically return, but the critical operational trait is disclosed.

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?

Four short sentences, front-loaded with purpose and the negative boundary, followed by the workflow step and the expiry caveat. No redundant restatement of the schema.

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 read-only quoting tool with a fully documented schema and no output schema, the description covers purpose, the do-not-book boundary, the handoff to request_ride, and quote lifetime. Only the shape of the returned options is unstated, a minor gap given the 'one per service type' phrasing.

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 origin, destination, second_destination and services are already fully documented, including accepted formats. The description adds only the framing that quotes are per service type, which the schema's parameter docs already imply.

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?

States a specific verb and resource ('Gets price and ETA quotes for a ride') and immediately scopes the return ('one per service type'). The negative clause 'Does NOT book anything' cleanly separates it from the sibling request_ride.

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?

Explicit sequencing: show the user the options, then call request_ride with the chosen quote. It names the alternative tool and the condition that selects it, leaving nothing to inference.

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