get_nse_indices

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

With no annotations, the description acknowledges it provides live data from the official NSE API and lists return fields. However, it lacks details on rate limits, freshness, or error handling, but is sufficient for basic understanding.

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 two sentences plus a bullet list, highly concise and front-loaded. No extraneous information; every sentence is useful.

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?

Given the simple schema (one optional param, no output schema), the description is sufficiently complete. It clarifies return fields and data source, though it omits potential timeout or pagination behavior.

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 coverage is 100% with a single 'filter' parameter described as filtering by name. The description adds value by providing example filter values (e.g., 'NIFTY', 'BANK'), enhancing understanding 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?

The description clearly states it returns live data for all NSE indices, lists specific index names, and specifies returned fields (open, high, low, etc.). This distinguishes it from sibling tools like get_nse_quote (single stock) or get_market_summary (broader market).

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 implies the tool is for accessing all indices or filtering by name, but it does not explicitly state when to use this over alternatives (e.g., get_nse_quote for a single stock) or provide any exclusion criteria.

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