option_snapshot_greeks_implied_volatility

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

With no annotations provided, the description must carry the full burden of behavioral disclosure. It only states the source prices (bid/mid/ask) but does not disclose any limitations, return format, pagination, rate limits, or handling of invalid inputs. The real-time nature is implied by the name and the phrase 'Real-time', but no additional behavioral context is given.

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 core function. Some words like '[STANDARD]' add no value, but the core message is efficiently delivered.

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 12 parameters, no annotations, no output schema, and a large set of sibling tools, this description is severely under-specified. It does not explain return values, filtering options, or relationship to other greeks tools, and lacks any guidance for proper usage in different scenarios.

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?

The input schema has 100% description coverage, with all 12 parameters documented including defaults, enums, and formats. The description does not add any parameter-specific meaning beyond what the schema already provides, so the baseline score of 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?

The description identifies the tool as providing real-time implied volatility computed from bid, mid, and ask prices, which clearly distinguishes it from sibling snapshot tools that return all Greeks or other specific data. However, it does not explicitly mention the tool's scope as an options snapshot, relying on the tool name and schema to convey that context.

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 provides no guidance on when to use this tool compared to the many related options snapshot tools, such as option_snapshot_greeks_all or option_snapshot_quote. There is no mention of use cases, exclusions, or alternative tools, leaving the agent without direction for tool selection.

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