Get current Tesla Robotaxi ride status

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

Annotations already provide readOnlyHint and openWorldHint, so the description is not burdened with basic safety disclosure. It adds useful scoping ('active' vs 'most recent terminal') but does not explain what happens if no ride exists or whether status can change between calls. This is acceptable but not rich.

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. It front-loads the action and the key semantic distinction between active and most recent terminal sessions.

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 zero-parameter read-only status tool with an output schema and helpful annotations, the description covers the essential behavior. The main gaps are the unexplained 'TripX session' terminology and a lack of explicit connection to sibling tools like ride_history.

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 tool has zero parameters, so there is no parameter documentation burden on the description. The schema fully covers this area, and the baseline for zero parameters is 4.

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 states a specific action ('Return') and a precise resource ('active ride or most recent terminal TripX session'), which goes beyond the title. It is reasonably distinguishable from siblings like robotaxi_ride_history, though it does not explicitly name the alternative.

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 phrase 'active ride or most recent terminal' implies when the tool is appropriate: for current or last-completed ride status. However, it does not explicitly contrast with robotaxi_ride_history or state when not to use this tool, leaving some selection inference to the agent.

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