get_index

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

No annotations are provided, so the description must fully disclose behavior. It indicates 'live data' but does not mention read-only nature, authentication requirements, rate limits, or any side effects. This is minimal behavioral disclosure for a data retrieval 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?

The description is three sentences, front-loading the core action and data returned. Every sentence adds value: purpose, common indices, and an example. No redundant or unnecessary text.

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 simple tool with one parameter and no output schema, the description covers purpose, parameter examples, and returned data. It lacks explicit mention of the return format (e.g., JSON fields), but otherwise is fairly complete for a live data query.

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 input schema has a single 'name' parameter with no description (0% coverage). The description compensates by listing common indices and providing an example ('NIFTY 50'), adding meaning beyond the schema. However, it does not clarify case sensitivity or exact format requirements.

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 the verb 'Get' and the resource 'live data for an NSE index', specifying the returned data (value, change, advances/declines). It lists common indices and provides an example, making the tool's purpose distinct from siblings like get_index_constituents or get_index_history.

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 usage for retrieving live NSE index data but does not explicitly state when to use this tool versus alternatives. No exclusions or conditions are provided, though the example and common indices list offer some guidance.

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