Preview Waymo ride cancellation

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

The description adds a key behavioral guarantee beyond the annotations: it will not cancel the active ride. This addresses the main destructive risk, especially since readOnlyHint is false but destructiveHint is false. It does not detail other potential side effects, but for a 0-parameter preview tool this is reasonably transparent.

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?

A single, front-loaded sentence that conveys purpose, target, and key non-effect with no wasted words. Every phrase earns its place.

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?

Given the tool has no parameters, an output schema, and a straightforward purpose, the description provides enough context for correct selection and invocation. The active-ride scoping and the explicit 'without cancelling' clarification make the behavior complete for an agent.

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 no parameters and schema coverage is 100%. The description still adds useful meaning by identifying that the operation targets 'the active ride,' explaining why no explicit ride identifier parameter is needed.

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 clearly states the specific action: previewing the cancellation and its fee. It also explicitly distinguishes this from actually canceling by adding 'without cancelling the active ride,' which separates it from the sibling waymo_cancel_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?

The description makes the usage context clear: use this when the user wants to know the cancellation cost before deciding whether to cancel. However, it does not explicitly name alternatives or state when not to use it, though the contrast with canceling is implied.

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