get_market_indices

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

No annotations are provided. Description does not disclose behavior like data freshness, rate limits, or whether the optional 'index' parameter filters results (only schema hints). Lacks information on response structure or limitations.

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?

Single sentence with front-loaded verb and resource. No redundant information, highly efficient.

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 no output schema and simple input, description does not specify return fields (e.g., code, value, change) or whether data is current/historical. Minimal but adequate for a simple list tool.

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 parameter description. The description adds no new meaning beyond examples (MASI, MASIX) but does not clarify how the parameter affects results (e.g., filter vs all). Baseline 3 is appropriate.

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 tool retrieves 'all market indices' from a specific exchange, with examples (MASI, MASIX). This distinguishes it from siblings like get_stock_quotes (individual stocks) and get_market_summary (likely aggregate).

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 on when to use this tool vs alternatives. Does not specify prerequisites or context for selection among sibling tools like get_market_summary or get_stock_quotes.

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