get_nse_option_chain

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

No annotations are provided, so the description must carry the burden. It states the tool returns data from the official NSE India API and lists the returned fields. However, it does not disclose whether the tool is read-only, error handling, or rate limits. With no annotations, this is adequate but not fully transparent.

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 concise paragraphs, front-loading the purpose and data fields. It avoids unnecessary words and is well-structured. Could be slightly more structured with bullet points for the data fields, but it is efficiently written.

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 output schema, the description does a good job listing the data fields and supported symbols. However, it does not explain the return structure (e.g., array of strike objects), pagination, or the behavior of the expiry parameter when omitted. There is room for more completeness given the complexity of option chains.

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 both parameters described. The description adds context about the output fields and valid symbols, which helps parameter understanding. However, it does not add extra detail beyond the schema for the parameters themselves, so 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 the tool gets the full F&O option chain for NSE stocks and indices, listing specific data fields and supported symbols. It distinguishes itself from sibling tools like get_nse_quote or get_market_summary by specifying the exact resource and verb.

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 mentions what symbols work but does not explicitly guide when to use this tool vs alternatives. No mention of when not to use or comparison with similar tools like get_nse_quote. The context is implied but not directly stated.

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