NSE end-of-day quote

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

Annotations already mark it read-only, idempotent, and open-world, and the description adds meaningful context beyond those: it emphasizes the data is SETTLED END-OF-DAY, warns against presenting it as the current price, and discloses the source as NSE's bhavcopy archive. It also lists the returned fields, which is valuable without an output 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?

The description is three tight sentences: purpose and source, a critical behavioral caveat, and usage plus return fields. Every sentence contributes meaning and there is no wasted wording.

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 simple two-parameter, read-only tool with no output schema, the description is complete: it names the data source, states the settled-data caveat, explains the default behavior for trade_date, and enumerates the returned metrics. Nothing essential for correct invocation is missing.

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 description coverage is 100%, and the schema already documents symbol examples and the ISO date format for trade_date including the 'omit for latest' behavior. The description mostly restates the trade_date guidance, adding little semantic value beyond what the schema provides.

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 returns end-of-day OHLCV for an NSE-listed stock from the official bhavcopy archive, so its core purpose is unambiguous. However, it does not explicitly differentiate itself from the sibling nse_eod_history, leaving the single-day vs. multi-day distinction implicit.

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 gives clear context: this is settled end-of-day data, not a live intraday price, and trade_date can be omitted for the most recent trading day. It does not explicitly name alternatives like nse_eod_history for historical ranges, so it stops short of full when-not guidance.

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