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

Annotations already establish read-only, idempotent, non-destructive, and non-open-world behavior, so the safety profile is covered. The description adds meaningful context: the exact data blocks returned, the 30-day daily window, and that chart data is optional and gated by a param — useful since no output schema exists.

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 verb and resource are front-loaded, and the bulleted inventory is scannable and dense with concrete content types. The final line ('Essential for understanding institutional money flow in Indian markets') is filler that does not earn its place.

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-required-param read tool with no output schema, the description adequately conveys what comes back and the effect of the optional param. The main remaining gap is the failure to differentiate from the sibling get_fii_dii_flows, which is a real selection hazard.

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% with a single documented enum param, so baseline is 3. The description reinforces its role ('Optional: cumulative flow chart data with interval param') but adds no syntax or default-value detail beyond the schema.

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?

States a specific verb and resource ('Get detailed FII/DII institutional flow data') and enumerates the exact data categories (cash flows, F&O positioning, aggregates, streaks, chart data). However, it never distinguishes itself from the near-identically named sibling get_fii_dii_flows, leaving the 'detail' scope ambiguous.

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?

There is no when-to-use, when-not-to-use, or alternative routing guidance. The existence of get_fii_dii_flows makes this a critical omission — an agent cannot tell which of the two FII/DII tools to pick. The closing sentence ('Essential for understanding institutional money flow') is a value claim, not usage guidance.

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