Get a Tesla Robotaxi quote

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

The description says 'Get a live fare,' which presents the operation as a read-only retrieval, yet the annotations declare readOnlyHint=false. This is an annotation contradiction; the description also fails to clarify whether the quote request has side effects or validity limits.

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 front-loaded sentence with no wasted words. It is concise, though 'for two Robotaxi locations' is slightly vague compared to saying 'between pickup and dropoff.'

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 4-parameter tool with a place-search sibling, the description omits the workflow (search places, then choose result indexes) and the relationship to book_ride. The output schema may cover returns, but the description is not complete enough for correct invocation in ambiguous-location cases.

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?

Only pickup and dropoff have schema descriptions; pickup_result_index and dropoff_result_index are undocumented. The description adds no meaning for the index parameters, so an agent cannot tell that they select among place-search results or how to use them.

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 names a specific operation—get a live fare and route preview—for two robotaxi locations, which clearly distinguishes it from sibling tools like search_places, book_ride, and ride_status. The verb 'Get' plus 'fare and route preview' makes the tool's outcome unmistakable.

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 purpose implies this is a pre-booking fare/route check, but the description never explicitly says to use it before book_ride or explains when not to use it. There are no stated alternatives or exclusions, so the agent is left to infer usage from the sibling names.

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