US Natural Gas Prices

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, and openWorldHint=true, so the description carries a lower burden. However, it adds only 'public domain' which is about data source, not behavioral context (e.g., auth needs, rate limits, or scope boundaries beyond what annotations imply).

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-sentence description is extremely concise and front-loaded, with zero superfluous text. Every sentence contributes directly to understanding the tool's purpose and data source.

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 has 5 optional parameters and an output schema, the description covers the core purpose but does not explain default behaviors (e.g., frequency defaults to monthly, length defaults to 24) or provide additional context about the output structure. It is minimally adequate.

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?

Input schema has 100% description coverage for all 5 parameters, so description bears minimal responsibility. The description mentions 'by US state', aligning with the state parameter, but adds no further meaning beyond what the schema already provides.

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?

Description clearly states the tool provides natural gas prices (residential/commercial/industrial) by US state from EIA public domain. It effectively distinguishes from sibling EIA tools like electricity, petroleum, and series by specifying the natural gas sector.

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 querying natural gas prices but provides no explicit guidance on when to use this tool versus alternatives (e.g., other EIA tools). No when-not-to-use or prerequisite information is given.

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