options_flow

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

With no annotations, the description carries the full behavioral burden and does so thoroughly. It discloses that the first call triggers background capture and returns warming with no trades, that the session covers the whole day, that symbols accepts a list or bare string, and that no buy/sell side is asserted unless the order was seen live.

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 longer than typical and uses emphatic caps, but it is front-loaded with the core purpose and each paragraph adds essential operational detail. It is structured and information-dense rather than padded.

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?

Without an output schema or annotations, the description supplies the return fields, filtering threshold, session timing, warming behavior, and directional caveat. An agent has enough context to invoke it correctly and interpret results.

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%, so the description must compensate. It explains min_premium as a dollar threshold and symbols as accepting a list or bare string. However, the limit parameter is not described explicitly, leaving a small gap despite the schema's title and default.

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 function: returning the largest option orders in the current session for given underlyings, sorted by premium, with an explicit list of returned fields. This clearly distinguishes it from sibling tools like option_chain or market_tape by its session-scoped, premium-sorted options-flow focus.

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?

It gives clear context: use this tool to see the largest option orders at or above min_premium, and it explains the session-wide capture and warming behavior. It does not explicitly name alternatives or state when not to use it, so it stops short of a 5.

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