nhtsa_recall_detail

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

Description adds context beyond annotations: returns full recall info including affected vehicles, summary, consequence, and remedy. Annotations already mark readOnlyHint=true, so no contradiction.

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?

Three sentences, front-loaded with purpose, efficient. No wasted 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?

For a single-parameter lookup tool with full schema coverage and no output schema, the description is nearly complete. Minor improvements possible: explicitly stating the parameter is required and must match format exactly.

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 parameter description. The tool description repeats the campaign number format and adds output info, but adds no additional semantic value to the parameter.

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 gets recall details by campaign number, with examples of the identifier format. It distinguishes from sibling tools that list recalls (nhtsa_recalls) or decode VIN, but does not explicitly differentiate.

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?

Implied usage: use when you have a campaign number. No guidance on when not to use or alternatives like nhtsa_recalls or nhtsa_decode_vin are missing.

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