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

No annotations present, so description carries full burden. It discloses data sources (public NHTSA/USCG), limitations (not official title), and return items (recalls, complaints, investigations, decode, next-step sources). No hidden behaviors remain.

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 paragraph but well-structured: main action first, then scope, then detailed contents, then caveats. Every sentence adds value without redundancy.

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?

Despite no output schema, the description enumerates all return elements (recalls with severity ranking, complaint counts, investigations, VIN check-digit, decode, next-step sources), making the tool's output fully predictable.

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% with descriptions for 'vin' and 'hin' parameters. The description adds context on when to use each (VIN for land vehicles, HIN for boats) and the character lengths, enhancing understanding beyond the schema.

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 specifies the tool generates a pre-purchase report for titled assets by VIN or HIN, lists vehicle types (cars, trucks, RVs, trailers, heavy equipment, recreational boats), and details the return data. The verb 'generate' and resource 'pre-purchase report' are 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 explicitly states when to use the tool (pre-purchase check), what data it covers (public NHTSA/USCG), and importantly distinguishes it from official title records, advising a state/NMVTIS check for lien/salvage. It provides clear alternatives.

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