nse_options_chain

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

With no annotations provided, the description carries the full burden. It discloses the returned data fields (strike price, premium, volume, OI, IV, PCR) and notes it is a [PRO] feature, but does not address error handling, rate limits, or explicitly confirm read-only behavior. This is adequate but not rich.

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 well-organized with a one-line summary, a list of returned fields, an args section, and examples. Every sentence adds value, and the structure is easy to scan.

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 single parameter and presence of an output schema, the description covers the essential aspects: what the tool does, what data it returns, and how to call it. Minor details like expiry selection or pagination are not addressed, but they are not critical for the tool's core functionality.

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?

The schema provides zero description for the 'symbol' parameter, but the description fully compensates by explaining it accepts NSE stock or index symbols and gives three concrete examples (RELIANCE, NIFTY, BANKNIFTY). This is sufficient for unambiguous invocation.

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 the tool retrieves options chain data for NSE stocks or indices, using a specific verb ('Get') and resource ('options chain'). This distinguishes it from siblings like options_oi_analytics or options_greeks, which focus on deeper analysis rather than raw chain data.

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 usage through examples (RELIANCE, NIFTY, BANKNIFTY) and clearly indicates it is for getting options chain data. However, it does not explicitly mention when to use this tool versus alternatives or any exclusions, so it lacks explicit selection guidance.

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