Get Refining & Trading Spreads

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

Annotations already indicate readOnlyHint=true and openWorldHint=true. Description adds the paid plan requirement, which is a behavioral constraint not in annotations. No contradictions.

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 concise sentences covering purpose, usage guidance, and prerequisite. No fluff; each sentence earns its place.

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?

Adequate for a simple read tool with one parameter. Covers purpose, usage, and prerequisite. Lacks detail on output format, but openWorldHint suggests dynamic data; completeness is good given low 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 provides enum with descriptions, but description adds context like 'crack spreads (refining margin proxy)' and examples, enriching semantics beyond the schema alone.

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 refining and trading spreads' with specific types (crack, basis, margin). Distinguishes from siblings like opa_get_price by focusing on spread calculations rather than spot prices.

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?

Provides explicit mapping to user queries: 'crack spreads, 3-2-1 crack, refining margins, basis differentials, or blend/transport margins.' Also notes prerequisite of a paid plan with energy intelligence access.

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