nrel_fuel_stations

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, and openWorldHint=true, so the safety profile is fully covered. The description adds scope context ('Covers all U.S. alt fuel infrastructure') but no additional behavioral traits such as rate limits, data freshness, or response shape. No contradiction with annotations.

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 front-loaded with the action and resource. The second sentence gives useful filter keywords. The fuel-type list is somewhat redundant with the schema and incomplete, but it remains a quick-reference aid rather than a major source of bloat.

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 fully documented parameters and strong annotations, the description is largely complete. The only notable omission is that there is no output schema and the description does not describe the response format, though this is not critical for basic invocation. Overall, the agent has enough to call and filter correctly.

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 all six parameters are already documented with types, enums, and descriptions. The description's fuel-type list partially duplicates the schema enum but omits LNG and RD; it adds no meaningful syntax or format details beyond the schema. Baseline 3 applies because the schema does the heavy lifting.

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 states a specific verb ('Search'), a concrete resource ('alternative fuel stations'), and a clear scope ('Covers all U.S. alt fuel infrastructure'). It also lists the fuel types covered, making it easy to distinguish from the sibling NREL tools (nrel_utility_rates, nrel_solar) and all other data sources.

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 implies when to use the tool ('Search for... alternative fuel stations') but provides no explicit guidance about when to prefer it over alternatives or when not to use it. No sibling alternatives are named, leaving the agent to infer based on tool names and semantics.

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