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

Annotations only say readOnly and openWorld; the description adds the facts an agent actually needs for a paid endpoint — the $0.002 USDC cost, the x402 payment rails (Base, Solana, Arc), and that failed calls are not charged. It also scopes the response to fields NHTSA holds and excludes recall/history, which is real behavioral disclosure beyond the annotations.

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 tight sentences: purpose first, output caveat second, pricing third. Every sentence carries information, though the pricing clause is dense enough that it could be split for readability.

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?

An output schema exists so return values need no prose, and the tool takes one fully documented argument. What remains — output scope, exclusions, cost and billing policy — is all present, leaving nothing an agent needs to call it correctly.

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?

Single parameter with 100% schema description coverage ("17-character VIN, letters I, O, Q not allowed"), so the schema already carries the semantics. The description only restates the VIN concept without adding format or validation detail, which is the baseline case when the schema does the work.

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?

Opens with a specific verb and resource ("Decodes a VIN with NHTSA vPIC") and then enumerates exactly what fields come back. This separates it cleanly from siblings like travel_nhtsa_vehicle_recalls, travel_nhtsa_vehicle_complaints and travel_carfax without the agent needing the 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?

The clause "no recall or history data" tells the agent when NOT to reach for this tool and implicitly routes it to the recall/history siblings, and "Only fields NHTSA has for that VIN are returned" sets expectations about coverage. It stops short of naming an explicit alternative, so it is clear context rather than full routing.

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