get_fii_dii

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

No annotations are present, so the description carries the transparency burden. It discloses the key behavioral scope: latest-day only, cash-market, NSE source, and rupee-crore units. It does not describe the response shape or edge cases such as missing data, but this is a simple zero-parameter read tool.

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?

A single front-loaded sentence packs the key facts: recency, instrument types, market segment, metric, units, and exchange. There is no fluff or redundancy.

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 no output schema, the description gives enough to know what the tool returns and its scope. It could briefly clarify the response format, but the named fields (buy, sell, net) make the returned data predictable.

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 no parameters, and the schema confirms this with an empty properties object. The description does not need to explain parameter meanings, so the baseline score of 4 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 precisely identifies the resource: the latest day's FII/FPI and DII cash-market buy, sell, and net flows in ₹ crore from NSE. It is immediately distinguishable from all sibling tools, none of which cover this specific data.

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 intended use is clear: call this tool when the agent needs the most recent FII/FPI and DII cash-market flow figures. It does not name alternatives or exclusions, but no sibling tool offers comparable data, so explicit routing guidance is less necessary.

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