eia_electricity

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

The readOnlyHint annotation already signals a safe read operation, and the description adds useful context about sector codes and data type units. However, it does not disclose default date ranges, pagination behavior, or response structure, which would be valuable beyond the 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 main purpose, followed by two efficient list-like lines for sectors and data types. Every sentence adds value, with no redundant fluff.

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 has 8 optional parameters and no output schema, so the description needs to explain return behavior. It provides sector and data type explanations, but lacks information about response structure, defaults, and pagination. The 'generation' inconsistency also leaves a gap in expected data types.

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 baseline is 3. The description adds units for revenue (M$), sales (MWh), and customers, and expands sector codes to full names, but it also introduces 'transportation (TRA)' which is not in the schema enum, and 'generation' which is not a data_type option, slightly undermining clarity.

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, which distinguishes it from sibling EIA tools like eia_petroleum and eia_natural_gas. However, it mentions 'generation' but the data_type schema only supports price, revenue, sales, and customers, creating slight ambiguity.

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 usage for electricity data queries by listing sectors and data types, but it does not explicitly state alternatives or when not to use this tool. With siblings like eia_state_energy and eia_total_energy, more explicit guidance would help.

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