nhtsa_recalls

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

The readOnlyHint annotation already signals a safe read operation. The description adds the constraint that 'All three parameters are required by the NHTSA API,' which is useful contextual behavior beyond the annotation. It does not contradict annotations, though it does not detail return format or pagination.

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 concise sentences plus a concrete example. The main purpose is front-loaded, and every sentence earns its place by adding required-parameter info, alternative tool references, or an illustrative example.

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 simple search tool with readOnlyHint and complete schema, the description adequately covers purpose, required parameters, alternatives, and an example. Since there is no output schema, a fuller description of the return shape would be ideal, but the tool is straightforward and the existing context is sufficient.

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?

Input schema has 100% coverage with descriptive property text and examples. The description's example mirrors schema values ('tesla', 'model 3', 2024) and does not add meaning beyond what the schema already provides. Baseline 3 is appropriate.

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?

Description opens with a specific verb+resource: 'Search NHTSA vehicle recalls by make, model, and model year.' It clearly defines the tool's scope and distinguishes it from siblings by pointing to nhtsa_recall_detail for specific campaigns.

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?

Explicitly states that all three parameters are required, and names alternatives: 'Use nhtsa_models to find valid models for a make, or nhtsa_recall_detail for a specific campaign.' This provides clear when-to-use guidance and alternative tool references.

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