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

Beyond the read-only, idempotent, open-world annotations, the description discloses that only the first 11 characters (or 14 for low-volume manufacturers) are sent to NHTSA's vPIC service and that the serial number is never transmitted. It also clarifies the important limitation that results are make/model/year recall campaigns, not vehicle-specific campaign inclusion or repair status.

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 front-loaded with the core action and remains a compact two-sentence paragraph despite covering validation, decoding, campaign lookup, and a key limitation. It is dense but every clause adds relevant context; minor indirectness comes from referencing vehicle_recalls for field details rather than stating them directly.

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 read-only, three-parameter tool with full schema coverage and no output schema, the description is complete: it explains the processing chain, what data is sent to NHTSA, what the output represents, and the key limitation an agent must relay about vehicle-specific confirmation. Nothing needed to call it correctly or interpret its scope is missing.

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 description coverage is 100%, so the schema already defines vin, limit, and detail thoroughly, including the enum values and bounds. The description adds contextual meaning about the VIN check digit and privacy of transmitted characters, but does not further explain the limit or detail parameters beyond what the schema already provides.

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 chain—checks, validates, decodes, lists—and clearly names the resource: a VIN and the resulting NHTSA safety recall campaigns. It distinguishes itself from vehicle_recalls by describing the VIN validation and decoding step, and from NHTSA's official VIN lookup by explaining that it does not confirm vehicle-specific campaign inclusion or repair status.

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?

It states the exact input condition (a VIN), explicitly excludes a common but unsupported use case (confirming whether this specific vehicle is included in a campaign or has been repaired), and points to the authoritative alternative at nhtsa.gov/recalls for that purpose. That is explicit when-to-use and when-not-to-use guidance with a named alternative.

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