options_oi_analytics

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

With no annotations provided, the description must fully disclose behavioral traits. It does not mention data freshness, rate limits, read-only nature, or any prerequisites/limitations. The listed 'Provides' items are more about output components than behavioral characteristics such as side effects or authentication needs.

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-structured with a clear title, a bulleted feature list, an Args section, and examples. It is front-loaded with purpose. The Sensibull marketing sentence is somewhat extraneous for an AI agent, but it does not detract significantly from overall clarity.

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 tool's moderate complexity and the presence of an output schema, the description adequately covers inputs and expected outputs. It lacks behavioral context (e.g., when to use vs alternatives) but is sufficient for a single-parameter tool with examples.

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 no description for the symbol parameter, but the description's 'Args' section defines it as 'NSE stock or index symbol' and gives concrete examples. This adds meaning beyond the raw schema, though it doesn't address edge cases like case sensitivity or exact symbol formats.

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's purpose as 'Advanced options OI analytics' and enumerates its key outputs: Max Pain, PCR trend, IV summary, top OI strikes. This distinguishes it from sibling tools like nifty_pcr_trend or nse_options_chain by offering a broader analytical package.

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 provides clear examples (NIFTY, RELIANCE, BANKNIFTY) and specifies it works for NSE stocks and indices. However, it does not explicitly mention when to prefer this tool over alternatives like nifty_pcr_trend or options_greeks, nor does it state any exclusions.

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