nhtsa_car_seat_stations

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

With readOnlyHint=true, the safety profile is already provided. The description adds useful behavioral context by explaining the alternative search modes and the role of the `miles` parameter in geo searches, which is beyond what annotations provide. It does not disclose potential edge cases, but this is acceptable given the tool's simplicity.

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 concise and well-structured, with the purpose stated upfront, followed by search modes, context, and a useful example. Every sentence earns its place, and there is no redundancy or fluff.

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 read-only search tool with no output schema, the description provides adequate context: it explains the purpose, search options, and gives an example. It does not cover what happens with conflicting parameters or the default behavior when no parameters are provided, but these are minor gaps for such a 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 input schema already provides 100% coverage with descriptions for all five parameters, so the baseline is 3. The description reinforces the alternative search modes but does not add substantial new meaning beyond the schema. The example is helpful but not essential.

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's function: 'Find car seat inspection stations near a location.' This is a specific verb-resource pair that uniquely identifies the tool and distinguishes it from sibling tools, as no other tool targets car seat inspection stations.

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 clear usage context by listing search methods ('by ZIP code, state, or geographic coordinates') and includes a concrete example. It does not explicitly mention alternatives or exclusions, but the context is sufficient for an agent to understand when to use this tool.

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