Book a Tesla Robotaxi ride

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

Annotations already indicate destructiveHint=true and readOnlyHint=false. The description adds a useful consent guardrail ('only after the user explicitly requests it'), but it does not disclose further behavioral details such as charging the payment method, consuming the quote, or irreversibility beyond what annotations already convey.

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 focused sentence with no filler. The key condition is front-loaded and every word contributes to the tool's safe invocation.

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 booking action, the description captures the critical gating condition: explicit user request. The input schema covers parameter provenance and the confirmation constant, and the output schema exists. It could still explicitly warn about charges or quote consumption, but overall it is sufficiently complete.

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?

Two of the three parameters already have schema descriptions identifying their sources (proposal_token from robotaxi_get_quote, payment_method_id from robotaxi_list_payment_methods), and confirmation is self-documenting via const 'BOOK'. The description adds no parameter-level meaning, but the schema coverage is adequate.

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 and resource: 'Book a quoted ride'. The phrase 'quoted ride' distinguishes this tool from robotaxi_get_quote and other ride-related siblings, and the explicit-request qualifier makes the action's scope clear.

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 clearly states when to invoke the tool: only after the user explicitly requests the booking. It implies the should-not-call condition (before explicit user request), though it does not explicitly name related tools or provide a detailed workflow with alternatives.

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