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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds real value beyond that: the upstream data source (NHTSA vPIC), the specific artifacts returned, and the fitment granularity limit (year x model x engine) that tells the agent what the result can and cannot resolve.

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 dense sentences: the action and returns come first, the modeling caveat second. Every clause carries information an agent needs; there is no boilerplate or restatement of the name.

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 single-parameter read tool with full schema coverage and rich annotations, the description supplies the remaining essentials: source, return contents, and the fitment limitation. No output schema exists, but the description already enumerates what comes back, so nothing material 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% and the schema already documents the 17-character, no-I/O/Q format, so the baseline is 3. The description goes slightly beyond by tying the parameter to its decode source and clarifying what the resolved vehicle dimensions mean for downstream fitment decisions.

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 and resource ("Decode a 17-character VIN") plus the data source (NHTSA vPIC) and enumerates the concrete outputs (engine platform, configuration pages, recalls and bulletins). None of the siblings (find_part_number, get_page, list_platforms) do VIN decoding, so an agent can route unambiguously without opening 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 description establishes a clear context for use (you have a VIN and need platform/config/recall data) and adds a scope caveat that "cab and wheelbase are not modeled." It does not explicitly name alternatives or state when to prefer find_part_number or list_platforms instead, so it stops short of a 5.

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