get_nse_intraday_data

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

No annotations are provided, so the description must carry behavioral weight. It conveys that this is a read-only data retrieval operation and specifies the exchange and metric ('most-active-by-volume/value'), but it does not disclose details such as whether data is delayed, whether it reflects current trading day, or what the output structure means.

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?

One short sentence with no filler or redundancy. The key qualifiers ('NSE', 'intraday', 'most-active-by-volume/value') are all present and front-loaded.

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 zero-parameter tool with an output schema, the description is largely sufficient. The only minor gap is that 'volume/value' is slightly ambiguous (could mean either or both), and no explicit distinction from the BSE sibling is named, but overall the tool can be invoked correctly with the information provided.

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 tool has zero parameters, so parameter semantics are trivially satisfied. The description does not need to explain parameters that do not exist, and no ambiguity is introduced.

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 uses a specific verb ('Get') with a clear resource ('NSE intraday most-active-by-volume/value data'). It is immediately distinguishable from the sibling tool get_bse_intraday_data by exchange, so an agent can select it appropriately.

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 phrase 'NSE intraday' clearly establishes when this tool applies versus the BSE-focused sibling. It does not explicitly name alternatives or exclusions, but the context is strong enough for a zero-parameter retrieval tool.

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