nrel_utility_rates

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

The annotation readOnlyHint: true already indicates the tool is read-only. The description reinforces this by stating it 'gets' data, but does not add further behavioral details (e.g., no data limits, no authentication needs). Overall adequate given the annotation coverage.

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 exceptionally concise: two single-line sentences that front-load the purpose and provide clear instructions. Every word adds value with no waste.

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 tool's simplicity (2 parameters, no output schema), the description covers the essential behavioral and parameter details. However, it does not describe the output structure beyond mentioning 'local utility and their rates ($/kWh)', leaving some ambiguity for an agent.

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?

The input schema covers both parameters (lat, lon) with examples, so the description's job is lighter. However, the description adds meaning beyond the schema by stating that the location is for U.S. and that rates are in $/kWh, which helps the agent interpret results.

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 gets electricity rates and specifies the sectors (residential, commercial, industrial) and location requirement (U.S. location). It distinguishes itself from sibling tools like nrel_fuel_stations and nrel_solar by focusing on utility rates.

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 clear context: provide latitude/longitude to get rates for any U.S. location. However, it does not mention when to avoid using this tool or provide alternatives for similar tasks, leaving it to the agent to infer from context.

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