nrel_fuel_stations

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

Annotations already declare readOnlyHint=true, so the description's additional context (covering all U.S. alt fuel infrastructure) adds some value but does not disclose behavioral traits like data freshness, pagination, or response shape. Given annotations cover the safety profile, the description is adequate.

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 with no wasted words. The first sentence front-loads the main purpose and coverage, and the second enumerates filters and fuel types efficiently.

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?

The description adequately defines the tool's scope and parameters, but it does not describe the output format or fields returned. Since no output schema is provided, this omission leaves some ambiguity for the agent about what data to expect.

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 descriptions for all parameters. The description lists fuel types and mentions radius filtering, adding marginal value 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 searches for EV charging stations and other alternative fuel stations across the U.S. It uses specific verbs like 'Search' and identifies the resource as alternative fuel stations, distinguishing it from sibling tools like nrel_solar and nrel_utility_rates which handle different data.

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 lists filter parameters (state, zip, fuel type, radius) and fuel types, providing clear context for when to use the tool. However, it does not explicitly exclude scenarios or mention alternative tools, though no direct competitors exist among siblings.

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