Cancel the active Tesla Robotaxi ride

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

Annotations already declare destructiveHint=true, and the description adds meaningful behavioral context: a fresh preview and explicit user confirmation are required before the destructive cancellation occurs. This goes beyond the structured annotations without contradicting them.

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 extremely concise, front-loaded, and contains no filler. Every word earns its place by communicating a necessary precondition.

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 one-parameter destructive tool with a rich output schema and annotations, the description is largely complete. It covers the safety-critical prerequisites and clearly distinguishes this cancellation action from the preview sibling. Minor details about cancellation effects are not stated, but the destructive annotation and output schema cover much of that burden.

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 schema already documents the single parameter with a required const of 'CANCEL'. The description adds the notion of 'explicit user confirmation,' which gives some semantic context, but with 0% schema description coverage it does little to independently document the parameter beyond what the schema's const and title already convey.

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 title clearly identifies the action ('Cancel the active Tesla Robotaxi ride'), and the description reinforces it with a specific verb and the required preconditions. It differentiates from robotaxi_preview_cancellation by making clear this tool performs the actual cancellation after a preview.

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 gives an explicit usage condition: only cancel after a fresh preview and explicit user confirmation. This effectively tells the agent when it is appropriate to invoke the tool, though it does not explicitly name alternatives or edge cases.

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