get_markets

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

No annotations are provided. The description only discloses that niche includes price returns over 1D-5Y and includes tjiid. It does not mention data freshness, rate limits, error handling, or other behavioral traits that the agent should know. Since annotations are absent, the description should carry more weight.

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 a single sentence that efficiently front-loads the purpose and uses a clear bullet-like structure for the three categories. Every part adds value without redundancy.

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 simplicity of the tool (one enum parameter, no output schema), the description covers the essential context: what each tab returns and links to sibling tools. It could mention typical output fields (e.g., name, value) but is sufficiently complete for agent decision-making.

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 0%, so the description must compensate. It successfully explains what each enum value returns: headline for major indices, niche for sector indices with price returns and tjiid, conglomerates for business groups with tjiid. This adds critical meaning beyond the schema's enum list.

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 specifies the verb 'Get' and the resource 'index performance'. It enumerates three distinct categories (headline, niche, conglomerates) and provides examples (Nifty/Sensex for headline, sector indices for niche, business groups for conglomerates). This clarity distinguishes it from sibling tools by mentioning tjiid links.

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 explicitly tells when to use each tab value and connects to sibling tools via tjiid. It could improve by stating when not to use this tool, but the clear mapping of tab values to specific data types provides adequate guidance.

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