opa_get_futures

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

No annotations provided, so description carries full burden. It describes the action but does not disclose any behavioral traits beyond that, such as data freshness, authentication needs, or side effects. However, as a simple read operation, the description is adequate and not misleading.

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 plus a list of contracts. Front-loaded purpose. The list is necessary due to the number of contracts, making it slightly longer but still 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?

Given one parameter, no output schema, and no annotations, the description covers the tool's purpose, usage context, and supported contracts. It does not describe the return format, but the tool name implies a price value. Sufficiently complete for a simple tool.

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 adds meaning by listing supported contracts with mappings (e.g., BZ/ice-brent = Brent). This provides context beyond the enum values in the schema.

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?

Clearly states 'Get the latest front-month futures contract price for energy commodities.' This is a specific verb+resource combination. Distinguishes from sibling tool opa_get_futures_curve by noting that for full forward curve, that tool should be used.

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 when to use: 'Use when the user asks about futures, forward prices, or contract prices.' Also provides alternative tool for full forward curve, giving clear guidance on when not to use this tool.

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