Search Tesla Robotaxi places

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds little behavioral context beyond the core transformation; it does not mention ambiguity handling, result ordering, or external geocoding behavior.

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 efficient sentence with no filler. The action and object are front-loaded, making the tool's purpose immediately scannable.

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 simple read-only search tool with an output schema, annotations, and reasonably descriptive parameters, the one-line description is nearly sufficient. It is slightly thin on how the resolved locations relate to downstream ride operations, but that is inferable from sibling tool names.

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 75%, with query, bias_latitude, and bias_longitude already documented. The description's phrase 'place name or address' largely duplicates the query schema description, and it does not clarify the 'limit' parameter beyond its name and default.

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 uses a specific verb ('Resolve') and clearly identifies the input ('a place name or address') and output ('Robotaxi locations'). It is easy to distinguish from the ride-status, booking, and payment sibling tools, none of which perform location search.

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 when to use this tool — when you have a place name or address to convert into Robotaxi locations — but it gives no explicit when-to-use or when-not-to-use guidance and does not name alternatives. An agent must infer its role in the ride-booking flow.

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