get_index_constituents

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

The description mentions 'live prices,' implying real-time or near-real-time data, but lacks details on update frequency, rate limits, or whether the output is cached. With no annotations, the description carries the full burden and only minimally discloses behavior.

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 concise (two sentences) and front-loaded with the core purpose. However, it could add slight details like valid index name formats without becoming verbose.

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 a single required parameter and the existence of an output schema, the description is adequate but not complete. It omits any mention of input validation or output structure details, which are partially covered by the schema.

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 'name' parameter has no description in the schema, and the description only provides an example ('NIFTY 50') without explaining valid values, case sensitivity, or format. This fails to compensate for the 0% schema coverage.

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 retrieves all stocks in an index along with live prices, using a specific verb ("Get") and resource ("stocks in an index"). It distinguishes itself from siblings like 'get_index' and 'get_index_history' which focus on the index itself rather than its constituents.

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?

No guidance is provided on when to use this tool versus alternatives, such as 'get_stock_quote' for individual stocks or 'get_index' for index details. The example is helpful but does not clarify context or exclusions.

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