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

With no annotations, the description carries the full burden of behavioral disclosure. It usefully states that results are YMM-scoped and that they never prove configuration identity, but it does not disclose side effects, authentication needs, VIN-handling behavior, or response characteristics. This is meaningful but incomplete context.

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?

Two sentences with no filler: the first fronts the tool's purpose and data categories, and the second adds an essential limitation. Every sentence earns its place.

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 tool with nine parameters, no annotations, and no output schema, the description is too sparse. It names the returned categories but does not explain parameter roles, query construction, or response behavior. An agent could know what data domain it is in, but not reliably how to invoke the tool correctly.

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 description coverage is only 22%, so the description should compensate for poorly documented parameters. It adds only indirect meaning: 'YMM-scoped' implies year/make/model are central, and 'never prove configuration identity' clarifies the limitation of configuration_id. However, it does not explain vin, trim, engine, drivetrain, or how the parameters combine.

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 uses a specific verb and resource: it returns NHTSA YMM-scoped recalls, complaints, investigations, communications, and safety ratings. The safety-data category and the caveat that these facts never prove configuration identity clearly distinguish it from siblings like get_vehicle_specs and resolve_vehicle.

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 gives an implicit usage signal: use this tool when NHTSA safety facts are needed. The statement that these facts never prove configuration identity provides a partial exclusion for identity-use cases, but it does not name sibling alternatives or state explicit when-to-use/when-not-to-use conditions.

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