nhtsa_car_seat_stations

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and openWorldHint=true, covering the safety profile. The description adds the search methods and example but does not describe response format, pagination, or any edge cases. It provides some behavioral context beyond annotations but not extensive.

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 plus an example, with the core purpose front-loaded. Every sentence adds value: purpose, search methods, context, and example. 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 simple lookup tool with no output schema, the description is sufficient. It explains the search modes and gives an example. It could mention precedence when multiple search parameters are given, but that is not essential for a straightforward 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?

Schema descriptions already cover all parameters with 100% coverage, so baseline is 3. The description adds the grouping of parameters (ZIP, state, or coordinates) and a concrete example, clarifying usage semantics beyond what the schema alone provides.

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 finds car seat inspection stations near a location, with explicit search methods (ZIP, state, coordinates). It distinguishes itself from sibling tools like nhtsa_recalls and nrel_fuel_stations by specifying the resource type.

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 lists search modes (ZIP, state, or lat/long) and provides an example with concrete values. It does not explicitly say when not to use it or mention alternatives, but the intended usage is clear from the context.

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