nrel_fuel_stations

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

Annotations include readOnlyHint=true, and the description's 'Search' verb is consistent. It adds scope context ('Covers all U.S. alt fuel infrastructure') and fuel type definitions, but does not disclose return format, pagination, or error behavior. With annotations covering safety, a 3 is appropriate.

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 compact and front-loaded with the core purpose. The fuel type list is somewhat redundant with schema descriptions but earns its place by providing plain-language mappings. No unnecessary filler.

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 6 parameters, full schema descriptions, and read-only annotations, the description covers the essential search scope and fuel types. It does not elaborate on response contents or combination rules, but the schema and annotations carry much of that burden.

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 coverage is 100% with detailed parameter descriptions. The description adds human-friendly fuel type expansions ('ELEC' → 'EV', 'HY' → 'hydrogen'), which aids agent comprehension beyond the raw schema enum values. This extra semantic value raises it above baseline.

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 opens with a specific verb 'Search for' and clearly identifies the resource: 'EV charging stations, hydrogen stations, biodiesel, CNG, and other alternative fuel stations.' It also distinguishes itself from siblings like nrel_solar and nrel_utility_rates by specifying alt fuel infrastructure.

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?

Provides clear usage context: 'Covers all U.S. alt fuel infrastructure' and lists the filter dimensions ('Filter by state, zip, fuel type, radius'). Does not explicitly name alternatives or exclusions, but for a search tool this is sufficient guidance.

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