NSE end-of-day history

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

Annotations already declare readOnly/idempotent/openWorld. The description adds non-obvious behavior: per-day archive files explain the range cap, and non-trading days are absent but counted in days_unavailable. This is meaningful beyond the schema.

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?

Three sentences with no filler; the core purpose, an important constraint, and a behavioral nuance are each addressed in one compact sentence.

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?

For a read-only historical data tool, it states what is returned (OHLCV series), the date range semantics, the cap, the alternative for longer ranges, and handling of non-trading days. No output schema exists, but the description covers the essential return concept well.

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 covers 100% of parameters with clear descriptions (ISO dates and NSE ticker). The description only restates the date-range idea and does not add parameter-level detail, so the baseline 3 applies.

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 opens with a specific resource: 'Daily OHLCV series for one NSE symbol over a date range.' This clearly identifies what the tool retrieves and separates it from sibling nse_eod_quote, which implies a single quote rather than a multi-day series.

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?

It gives explicit boundaries: a 120-calendar-day cap and a redirect to a pre-built warehouse for multi-year history. It does not explicitly contrast with sibling nse_eod_quote, so it misses full alternative routing, but the usage context is clear.

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