carvana_get_offer

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

No annotations are provided, so the description carries the full burden. It does disclose the important outcome variability — "Returns the offer if Carvana shows one, otherwise next steps" — which is real value. It says nothing about whether this requires user identity/consent, how long it takes, or whether it is strictly read-only, which matters for a tool that likely submits vehicle/owner data.

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?

Three short sentences, front-loaded with purpose then input requirements then outcome. Nothing is redundant, though the final clause is slightly compressed and could be tighter about what "next steps" means.

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?

No output schema exists, and the description covers both branches of the return (offer or next steps), plus the identifier inputs for a 5-parameter tool. It is close to complete; only auth/consent expectations and how zip and mileage influence the offer are absent.

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 100%, so the baseline is 3, but the description adds meaning the schema cannot: the either/or input rule "VIN or license plate + state," which tells the agent that no parameter is strictly mandatory but one identifier set is needed. It omits zip and mileage, which the schema documents as affecting the offer amount.

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 with provider scope: "Get a cash offer from Carvana for selling or trading in your car." That clearly separates it from the inventory/search siblings, though it never acknowledges carmax_get_instant_offer as the competing offer tool, so the Carvana-vs-CarMax boundary is left implicit.

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 "for selling or trading in your car" implies the situation, which is enough to pick this over carvana_search_inventory or carvana_get_vehicle_details. But with carmax_get_instant_offer in the sibling set, a genuine alternative exists and the description gives no when-to-use-this-vs-that guidance or exclusions.

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