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

Annotations already declare read-only, idempotent, non-destructive behavior. The description adds useful context: it returns specific vehicle attributes and is from NHTSA with no auth limits. No contradictions with 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?

Two sentences: the first lists outputs, the second covers source and constraints. Extremely concise and front-loaded with essential information, no unnecessary words.

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?

Given the existence of an output schema, the description fully covers the tool's purpose, input, and usage context (government source, unlimited, no auth). No gaps for an agent to invoke this tool 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?

The schema covers the single 'vin' parameter with length constraints. The description reinforces the 17-character requirement and lists decoded outputs, adding semantic value beyond the schema for the return, but the parameter itself is well-documented.

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 clearly states the tool decodes a 17-character VIN and lists the output attributes (make, model, year, etc.). It distinguishes from siblings like vehicle.vin.models by specifying the NHTSA source and the decode operation.

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 notes it uses US Government open data, is unlimited, and requires no auth, implying free and authoritative use for any VIN. However, it does not explicitly compare with alternatives like vehicle.autodev.vin_decode, so agents may need to infer when this is the best choice.

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