opa_get_futures_curve

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

No annotations provided, so the description carries the full burden. It states the output ('Returns a table of contract months with settlement prices, plus market structure analysis') but does not disclose any behavioral traits such as data freshness, rate limits, or side effects. For a clear read operation, this is adequate but could be improved.

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 sentences: first states purpose, second gives usage guidance and lists commodities. It is concise and front-loaded. Could be slightly improved by listing commodities in bullet points, but overall efficient.

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 tool with one optional parameter and no output schema, the description explains purpose, when to use, supported commodities, and basic output format. This is fairly complete for its complexity.

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 description coverage is 100%, with the schema already listing all enum values and their meanings. The description adds 'plus market structure analysis' but does not add meaningful parameter semantics beyond the schema. 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?

Description clearly states 'Get the full futures forward curve showing prices across all contract months.' It specifies the verb (Get) and resource (futures forward curve), and distinguishes from siblings like opa_get_futures and opa_get_spread by emphasizing the curve and term structure.

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 the forward curve, contango/backwardation, or term structure.' It also lists supported commodities, which implies when not to use (if commodity not in list). No explicit exclusions but clear context.

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