nhtsa_complaints

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

Annotations already declare readOnlyHint=true, so the description adds context that the NHTSA API requires all three parameters and provides an example. No additional behavioral details like pagination or rate limits are given, but the bar is lowered due to 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?

The description is extremely concise, uses a single paragraph with front-loaded purpose, and includes an example without any fluff. Every sentence is essential.

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 no output schema, the description covers the search purpose, required parameters, and even links to a sibling for model lookup. It is fairly complete but could mention response type or limitations.

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% parameter description coverage, so the description adds only the required nature and the NHTSA API requirement, plus an example. This adds marginal value beyond the schema descriptions.

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 it searches NHTSA vehicle complaints using make, model, and year. Among siblings, nhtsa_models is differentiated as a helper, and nhtsa_complaint_detail provides details, so the tool's specific role is well-defined.

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 explicitly states that all three parameters are required and recommends using nhtsa_models to find valid models, which provides clear usage guidance. While it doesn't explicitly mention when not to use this tool, the sibling reference covers alternatives.

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