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

Annotations already declare readOnly/openWorld/non-destructive, and the description adds genuinely new behavioral context the annotations cannot convey: a per-call price ($0.0035 USDC), the x402 payment path and supported chains, that compliant clients pay automatically, and a free sample call. Cost and payment obligation are exactly what an agent needs before invoking.

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?

Front-loads the core action and decoded fields, then tucks pricing/payment and the sample at the end. Slightly dense with a long field enumeration and payment boilerplate, but every sentence carries usable information.

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?

With no output schema, the description compensates by listing the returned fields, and it covers validation rules, coverage limits, cost, and a sample invocation. Nothing material for correct invocation 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 coverage is 100%, so the baseline is 3; the description goes slightly beyond by supplying a concrete valid example input ({"vin":"1HGCM82633A004352"}) that an agent can use as a template. The rest ('17-character VIN', required) merely repeats 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?

States a specific verb+resource (decode a 17-character VIN via NHTSA vPIC) and then enumerates the decoded fields (make, model, trim, engine, plant, etc.), so the agent knows exactly what comes back. No sibling tool does VIN decoding, so the scope is unambiguous.

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?

Gives a clear usage condition: 'Best coverage for vehicles sold in the US,' plus the format/check-digit requirements that gate a successful call. No alternative tool exists to route to, but it also doesn't state what happens for non-North-American VINs (soft failure vs. error), leaving one inference.

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