eia_electricity

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

Annotations provide readOnlyHint=true, so the agent knows it's a safe read. The description adds no further behavioral context (e.g., rate limits, pagination, default behaviors). Schema parameters describe defaults, but the description itself adds minimal behavioral info.

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 brief and front-loaded with the purpose, followed by a concise enumeration of sectors and data types. Every sentence adds value with no redundancy.

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 explains the core functionality and key parameters. However, given the 8 optional parameters and no output schema, it could briefly mention default date ranges or pagination behavior. Still, schema descriptions cover many details, making it largely complete.

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 parameter descriptions. The description adds value by listing example sector codes (RES, COM, etc.) and data type units (cents/kWh, M$, MWh, customers), which enriches understanding beyond the schema's enum 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 clearly states the tool retrieves electricity retail prices, generation, or consumption by state and sector. It lists specific sectors (RES, COM, IND, TRA, ALL) and data types (price, revenue, sales, customers), distinguishing it from sibling tools like eia_natural_gas or eia_petroleum.

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 the tool is for electricity data but does not explicitly state when to use it over alternatives or provide when-not-to-use guidance. Sibling tools exist for other energy types, but no comparison or exclusion is mentioned.

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