eia_natural_gas

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

The description adds meaningful context beyond the readOnlyHint annotation by disclosing the specific data series available (citygate, electric power, commercial, industrial, residential, Henry Hub spot) and their corresponding process codes. It does not contradict the annotation, but it omits details on units, output format, or data granularity, which would be useful.

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 two concise sentences: the first clearly states the purpose, and the second compactly lists process codes and their meanings. There is no fluff, and the information is front-loaded for quick parsing by an AI agent.

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 data retrieval tool, the description covers the essential options (price series and process codes). It is slightly incomplete in not clarifying how it differs from sibling EIA data tools, which would help an agent decide when to invoke it, but it does not need to explain return values since there is no output schema.

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?

While the input schema has 100% description coverage, the tool description adds critical value by including the PNG code for Henry Hub spot, which is missing from the schema's process parameter enum. It also reiterates the meaning of the codes, reinforcing and supplementing the schema descriptions.

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 natural gas prices and enumerates specific price categories (Henry Hub spot, citygate, residential, commercial, industrial, electric power). It distinguishes itself from sibling EIA tools (e.g., eia_petroleum, eia_electricity) by explicitly naming natural gas as the resource.

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?

No guidance is provided about when to use this tool versus alternatives like eia_petroleum or eia_total_energy. The description lists process codes but does not explain selection criteria or context for choosing this data source over other EIA datasets.

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