Get EIA Oil Inventories

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

Annotations already declare readOnlyHint=true and openWorldHint=true, which this description complements by detailing return options (latest weekly figures, summary, breakdown) and the paid plan requirement. Could further mention data update frequency or that it's from EIA, but overall adds value beyond 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?

Three sentences that efficiently convey purpose, usage, and output options. No fluff. First sentence defines the core action, second defines usage triggers, third details output views and prerequisite. Well-structured.

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 one-param read tool, the description covers purpose, usage, output types, and a prerequisite (paid plan). It could be improved by mentioning data source (EIA) and typical update frequency, but it is 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% (only one parameter 'view' with full enum and description). The description repeats the view values and meanings but does not add new parameter semantics beyond what the schema already provides, so 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 'Get the latest EIA weekly petroleum inventory (stocks) data,' with specific use cases (oil inventories, crude stocks, weekly EIA stocks, inventory builds/draws, product-level inventory levels). It distinguishes from siblings like opa_get_price or opa_get_storage by focusing on inventories.

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?

Explicitly says 'Use when the user asks about...' followed by a list of topics. It does not explicitly state when not to use or provide alternative tool names, but the sibling list implies other tools for non-inventory queries. Also notes the paid plan requirement.

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