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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=true), so the bar is lower. The description adds real context beyond them: it scans only the soonest few expirations, filters strikes below min_volume, and returns sorted-by-V/OI results. It doesn't mention rate limits or latency, but the operational behavior is well disclosed.

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?

Front-loaded with the core concept (V/OI ratio) and usage before the Args and Returns blocks. It is somewhat long, but the sectioning makes every line scannable and functionally useful, with little redundancy.

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?

There is no output schema, but the description compensates with a detailed Returns block enumerating underlying_price, expiries_scanned, aggregate volumes, put_call_volume_ratio, and each contract field including moneyness. An agent has everything needed to call and interpret 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 coverage is 0%, so the description carries the full burden, and it does: symbol is defined as a US stock ticker with examples, top_n and expiries have their defaults and meaning explained, and min_volume is explained as a noise filter for illiquid strikes. Every parameter gains meaning beyond the bare schema.

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?

States a specific resource and metric ('Top strikes by volume / open-interest ratio') rather than a vague 'options data' claim, and clarifies it is a positioning signal. An agent can distinguish it from the sibling stock_options_chain, which returns the full chain.

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?

Gives explicit trigger phrasing ('any unusual options activity on X?', 'where is the smart money positioned...') and the use case (a V/OI screener). It stops short of naming the alternative tool (stock_options_chain) or stating when NOT to use it, so it is clear but not fully routing.

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