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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, open-world). The description adds genuinely useful context beyond them: the data provenance guarantee that every grid point is a real listed contract rather than interpolated, which tells the agent this is a fidelity-critical data source. It stops short of stating latency, caching, or how many expirations are included.

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?

One sentence with no filler beyond the thrice-repeated 'real', which does emphasize the anti-fabrication guarantee but reads as insistence rather than specification. The sentence is not front-loaded with a verb, so the agent parses the artifact before the action.

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?

With no output schema, the description is the only source of information about what comes back, yet it never describes the grid's axes (strikes vs. expirations), shape, or return structure. For a read-only one-parameter tool this is adequate to select it, but not to know what to expect in the payload.

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?

There is a single parameter, ticker, and the schema already documents it at 100% coverage, so the description carries little extra burden. The description adds nothing about ticker format (exchange suffix, case) or option-chain availability constraints; baseline 3 applies.

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 specific resource: an implied-volatility surface grid derived from a fetched options chain across several expirations. It is clearly distinct from siblings like track_gamma_squeeze_mechanics or mandelbrot_fractal_analysis, though it is phrased as a noun phrase rather than an action verb, so what the tool *does* is implied rather than stated.

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?

There is no guidance on when to call this versus the other analytics tools, no prerequisites (does it need a live market session or a subscribed options feed?), and no stated exclusions. The agent must infer usage entirely from the description's subject matter.

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