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

Annotations already cover read-only, idempotent, non-destructive behavior, so the description does not need to restate those. It adds useful scoping language ('near a location') and a fuel-type list, but it does not disclose output format, data source limitations, or behavior around defaults beyond what the schema already specifies.

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 long and front-loads the core action with the resource and fuel types. The second sentence about target users adds useful context but is slightly auxiliary, preventing a perfect score.

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 rich input schema and annotations, the description provides enough context for an agent to identify and invoke the tool. It could be more complete by noting the US-centric scope and the explicit requirement to provide either location or lat/lon, but those details are recoverable from the schema.

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 100%, so the schema already documents all eight parameters clearly. The description adds user-friendly fuel-type labels but does not meaningfully expand on parameter semantics such as the location-or-lat/lon requirement, radius defaults, or status values.

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 ('Find') with a clear resource ('alternative fuel stations near a location') and enumerates supported fuel types, making the tool's purpose immediate. It also implicitly distinguishes itself from sibling NREL tools like solar or utility-rate lookups and from station-detail tools by focusing on location-based searches.

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 context on who would use this tool ('route planning agents, fleet operators, EV/clean-fuel tech') and makes the primary use case clear. However, it does not explicitly say when to choose this tool over related alternatives such as nrel_alt_fuel_station_detail, nor does it mention exclusions or prerequisites like needing a location or lat/lon pair.

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