get_markets

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

No annotations provided, but description discloses output structure (rows with tjiid) and behavioral traits like linking to other tools. Importantly, it does not contradict any annotations (none present) and provides adequate transparency for a read 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?

A single sentence that is well-structured, front-loads the purpose, and packs in specific details without being verbose. Every phrase adds value.

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 tool with one parameter, no output schema, and no annotations, the description is remarkably complete. It explains all tab options and the structure of the returned data, including links to sibling tools for further drill-down.

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 single parameter 'tab' has enum values, and the description adds significant meaning by explaining what each value returns (e.g., headline for Nifty/Sensex, niche for TJI indices with returns, conglomerates for business groups). This compensates for the 0% schema description 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?

Description clearly states it retrieves index performance with three specific categories (headline, niche, conglomerates), giving examples like Nifty/Sensex. It distinguishes from siblings by mentioning tjiid for linking to get_sector_constituents and get_conglomerate_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?

Usage context is implied through the description of data returned and links to sibling tools, but there is no explicit guidance on when to use this tool over alternatives or any exclusions.

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