get_option_chain

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

Description details the returned data fields (strike, bid/ask, last, volume, open interest, implied volatility, in-the-money flag) and notes default expiration behavior. Despite lacking annotations, this provides sufficient transparency for a read operation.

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?

Two sentences convey purpose, parameter details, and return data efficiently. No extraneous information, well-front-loaded with purpose.

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 no annotations and no output schema, the description covers essential aspects: what the tool does, parameter behavior, and return fields. Minor gaps like error handling or invalid symbol behavior, but generally complete for a standard data retrieval tool.

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?

With 0% schema description coverage, the description compensates by specifying expiration format and default. Symbol is self-explanatory but not elaborated. Overall, it adds meaningful context beyond the 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?

Description clearly states the tool retrieves option chain data (calls and puts) for a symbol and expiration date. This is a specific action with a well-defined resource, distinguishing it from siblings like get_option_expirations which only provide expiration dates.

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 explains the expiration parameter format and default behavior, and references get_option_expirations as the source for valid dates. While it does not explicitly list when not to use the tool, the context implies its appropriate use case.

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