nhtsa_models

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

The annotation readOnlyHint=true already signals a safe read operation, so the description doesn't need to state that. The description does clarify that omitting issue_type changes the data source (vPIC database) and that issue_type='r' returns models with recalls, adding useful context beyond the schema. However, it doesn't disclose pagination, response structure, or any rate limits.

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 two sentences plus an example, with no filler. It front-loads the primary use case, then clarifies the alternative mode, and includes a concrete example. Every sentence adds value.

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 has 3 parameters, no output schema, and a readOnlyHint annotation, the description is quite complete. It covers both modes of operation, uses an example, and clarifies the issue_type semantics. Minor gap: it doesn't explain what fields the returned model list contains or how results are ordered/sorted, but this is not critical for a list tool.

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?

The schema covers all three parameters with descriptions (100% coverage), so the description's example adds marginal value. It reinforces that issue_type is optional and model_year is optional, but the schema already conveys this. The description's example is helpful but not critical beyond the schema.

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 year, with an optional issue_type filter for recalls or complaints, and a fallback to list all models from the vPIC database when issue_type is omitted. The verb 'List' and specific resources ('vehicle models', 'make', 'year', 'recalls/complaints') make the purpose unambiguous and distinct from siblings like nhtsa_makes and nhtsa_model_years.

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 provides an example and explains when to use the issue_type parameter, implying that it is used for recalls/complaints vs. general model lookup. However, it does not explicitly state when to prefer this over sibling tools like nhtsa_recalls or nhtsa_complaints, nor does it mention any alternatives for broader queries.

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