EIA Total-Energy Series

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive. The description adds value by stating 'EIA public domain' indicating open data and 'Direct fetch' implying no authentication. It provides example IDs, but does not cover rate limits, error handling, or response pagination.

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 a single sentence with 20 words, efficiently conveying the tool's action and providing examples without unnecessary words. It is front-loaded with the purpose.

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?

With a complete output schema, annotations, and good schema coverage, the description is adequate. It mentions the data source and public domain nature. Could briefly explain 'total-energy' scope, but examples suffice. No major gaps.

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% and the description does not add parameter-level details beyond what the schema provides (e.g., series_id, frequency, length). The examples in the description reinforce the schema but are not necessary. Baseline 3 is appropriate.

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's purpose: direct fetch of any EIA total-energy time-series by series ID. It gives concrete examples (RNGWHHD, ELETPUS) and distinguishes from sibling tools (e.g., finance.eia.electricity) by specifying it covers 'total-energy' series specifically.

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 total-energy series through its title and examples, but does not explicitly state when to use this tool versus siblings (e.g., finance.eia.natural_gas). No 'when not to use' or alternative tools are mentioned, though the context of sibling names provides some differentiation.

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