options-chain

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

With no annotations, the description carries full burden. It discloses that data is delayed, free, and from CBOE. It lists return fields, implying a read-only operation. While it doesn't discuss error handling or rate limits, it provides sufficient behavioral context for a data retrieval tool.

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 two sentences with no wasted words. It front-loads the primary action and data source, then lists key return fields and filtering options. Every sentence adds value.

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 the simple data retrieval nature, no output schema, and high parameter coverage, the description adequately explains what the tool returns and how to use it. It could mention the response format (array of contracts) but is still complete for an agent to invoke correctly.

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 100% with detailed parameter descriptions. The description adds no extra meaning beyond the schema, merely restating that filtering by expiration and type is possible. Baseline 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 clearly states it returns a CBOE delayed options chain for any US equity or index, listing specific data fields (stock price, IV, greeks, OI, volume, bid/ask). This distinguishes it from sibling tools like 'options-snapshot' and 'stock-brief' by specifying the data scope and source.

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 implies when to use (for delayed options chain data without API key) and mentions filtering by expiration and call/put. It does not explicitly exclude other scenarios or name alternatives, but the context of finance-related siblings provides implicit guidance.

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