Index details and constituents

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

Annotations already declare readOnlyHint, openWorldHint and idempotentHint, so the safety profile is covered. The description adds useful behavioral context about what is returned, but says nothing about truncation from the limit parameter or the cost/shape of the constituent-heavy response, which matters for a tool that can return up to 500 rows.

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 that packs the output contents efficiently with no filler. Slightly dense, but every clause earns its place by describing a distinct data category.

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?

With no output schema, the description carries the burden of describing the return and does so thoroughly across both index-level and constituent-level fields. The one gap is that 'every constituent's ... approximate weight' understates the limit default of 50, so an agent might assume it always returns the full roster.

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%, so index codes, limit bounds and the sort enum are already fully documented in the schema. The description adds no parameter-level detail (e.g., that 'fno' is an accepted alias or how weight-sorting interacts with limit), so 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 names a specific resource (an NSE index) and enumerates the exact payload: level, returns, valuation ratios, breadth, and per-constituent price/change/weight. That is enough to separate it from get_quote (single security) and get_market_overview (broad market), though it never explicitly contrasts with those siblings.

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 statement of when to reach for this tool versus get_market_overview, get_quote, or search_securities, and no prerequisites or exclusions. Usage must be inferred entirely from the content list.

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