Get Vol Surface Metrics

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 discloses the output type (diagnostics) but does not state return format, any data source caveats, or whether parameters beyond base_coin are supported. For a tool with nested output schema, more behavioral context is needed.

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 a single concise sentence that front-loads the main purpose and key metrics. It earns its place without unnecessary elaboration, though it could add a brief usage note without becoming verbose.

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 the tool has a nested output schema and one parameter, the description is adequate for a simple diagnostic tool but not complete. It lacks detail on output structure or edge cases, but the presence of an output schema partially mitigates this.

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 0%, meaning the base_coin parameter's description only says 'Base cryptocurrency'. The tool description does not add any parameter-specific guidance, leaving the agent to infer the default and possible values. This is a missed opportunity to compensate for low 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?

The description states a clear verb ('Get') and resource ('volatility surface diagnostics') and lists specific metrics (RR, skew, vol-of-vol, VRP). This distinguishes it from sibling tools like get_skew_analysis or get_iv_rv_spread, though it does not explicitly name them.

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 implies usage for volatility surface diagnostics, but provides no explicit guidance on when to use this tool versus alternatives like get_skew_analysis or get_iv_rv_spread. The context is clear enough for an expert but lacks exclusions or alternative routing.

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