opa_get_oil_inventories

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

No annotations are provided, so the description carries the full burden. It states the tool returns 'the latest weekly figures' and optionally summary or by-product views, but lacks details on data recency, caching, or limits. The paid plan mention is good, but more behavioral context would improve transparency.

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 three concise sentences, front-loaded with the core purpose, followed by usage guidance and parameter explanation. No extraneous content.

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 tool with one parameter and no output schema, the description covers purpose, usage, and parameter options adequately. Minor gap: could briefly mention the return format or that data is from EIA.

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% with full descriptions for the single parameter. The description adds value by explaining what each view returns (e.g., 'headline totals + week-over-week change' for summary), complementing the schema enum values.

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 explicitly states 'Get the latest EIA weekly petroleum inventory (stocks) data', providing a specific verb and resource. It also lists use cases, clearly distinguishing from sibling tools that deal with prices, alerts, or other energy topics.

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 clearly indicates when to use the tool (e.g., 'when the user asks about oil inventories...') and mentions the paid plan requirement. It does not explicitly state when not to use it or provide alternative tools, but the context from sibling names is sufficient.

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