Change the destination

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

Annotations already flag destructiveHint=true and openWorldHint=true, so the safety profile is partly covered; the description adds real value by disclosing the mandatory two-step confirmation flow and the requirement that the passed price match the current preview. It stops short of saying whether the previous destination is recoverable or what happens if the price no longer matches the preview.

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?

Two short sentences, front-loaded with the action and followed by the gating condition. Every clause carries operational weight; nothing is padding.

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 destructive mutation with no output schema, the description covers the essential safety-critical flow (preview first, user consent, matching price). It leaves out the outcome of a successful call and the failure behavior on a price mismatch, which are the remaining gaps an agent would want.

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 coverage is 67%, and the description largely restates what the schema already documents about confirmed_price_toman ("Must match the current preview"). It does implicitly explain why ride_id is optional by scoping the operation to "the active ride," but adds no format or validation detail beyond the structured fields.

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?

States a specific verb and resource ("Changes the active ride's destination") and immediately names the sibling that must precede it (preview_destination_change), so an agent can distinguish it from the preview tool without opening either schema.

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?

Gives an explicit precondition ("Only call after preview_destination_change") plus a second condition ("the user agreeing to the new price"), which effectively names the alternative to use when that condition is unmet. Nothing about when to invoke it is left to inference.

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