get_iv_rv_spread

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

No annotations provided; description only covers purpose. Lacks disclosure of side effects (assumed read-only), authorization needs, rate limits, or any behavioral context beyond computation.

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?

Single sentence front-loads core purpose and context. No extraneous information.

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 compute tool with schema and output schema, description provides adequate purpose but lacks usage guidelines and behavioral details. Output format not described, though schema may cover it.

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 descriptions already explain base_coin and rv_window meaning. Description adds no additional parameter context; baseline 3 given high schema coverage.

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 it computes IV-RV spread (ATM implied vol vs Garman-Klass realized vol) and positions it as key for vol-selling strategies. This distinguishes it from sibling tools like get_vol_surface_metrics or get_skew_analysis.

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?

Implied usage via description ('key metric for vol-selling strategies') but no explicit guidance on when to use versus alternatives, no when-not or prerequisites stated.

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