nrel_utility_rates

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

Annotations declare readOnlyHint=true, so the read-only nature is already known. The description adds transparency by disclosing the output content: the local utility and rates in $/kWh. It also implies the tool performs a geographic lookup to identify the applicable utility, useful behavioral context beyond the annotation.

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?

Two concise sentences with the key action and input requirement front-loaded. Every phrase adds value: the types of rates, the geographic scope, and the unit of rate output. No redundancy or 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?

The tool is simple with only two required parameters and no output schema. The description provides enough context for an agent to select and invoke it: it covers the data type (electricity rates), the return unit, and the input format. It does not specify if all three rate classes are always returned, but given the description lists them, this is a minor gap.

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 examples in parameter descriptions, giving the baseline of 3. The description adds semantic value by explicitly tying the coordinates to the lookup of the local utility, clarifying that the parameters are not just numbers but geospatial locators. This exceeds the 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 uses a specific verb ('Get') and clearly identifies the resource ('residential, commercial, and industrial electricity rates for any U.S. location'). It distinguishes itself from sibling tools like nrel_solar and nrel_fuel_stations by scoping to utility rates, and also notes the input coordinate system.

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 clearly states the required input ('Provide latitude/longitude') and the expected outcome ('to get the local utility and their rates'), giving clear context for when to use the tool. It does not explicitly mention alternatives or exclusions, but the 'any U.S. location' phrasing and focus on rates makes usage conditions unambiguous.

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