Vehicle Models by Make/Year (NHTSA)

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

Annotations already provide readOnly, non-destructive, idempotent, and open world hints. The description adds the data source (NHTSA) but no additional behavioral traits beyond what annotations convey.

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?

Single sentence, front-loaded with action, no redundant words. Efficient and clear.

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 tool is simple, parameters are fully described in schema, output schema exists, and annotations are comprehensive, the description is adequate. It adds data source and optionality context.

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 descriptions cover both parameters. The description adds the explicit example 'Honda 2024' and indicates optionality ('a make and/or year'), which is not fully captured by schema alone.

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 lists vehicle models for a make and/or year, with an explicit example (Honda 2024). It uses a specific verb and resource, distinguishing it from sibling tools like VIN decoding or safety recalls.

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 implies usage when a make/year is known, but does not explicitly contrast with alternatives or provide when-not-to-use guidance. No reference to sibling tools is given.

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