getMarketIndicatorPrices

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

Annotations already indicate read-only and idempotent behavior. The description adds batch limit (200), delimiter (comma), error code (400), and rate limit group, providing useful context beyond annotations. No contradictions.

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 compact with a clear structure: title, purpose, batch limit, symbol constraints, error note, rate limit, and tag. Information is front-loaded. Minor markdown verbosity does not detract significantly.

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 retrieval tool with one parameter and no output schema, the description covers key aspects: purpose, supported symbols, limits, error handling, and rate limits. It does not detail the response structure, but the output is likely obvious price data given the name and context.

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 100% description coverage for the single parameter, already specifying symbol format, limit, and example. The description adds the symbol catalog reference and error handling, but these are minor extensions to the schema's own description.

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 '조회' (retrieve) and the resource '시장 지표 현재가' (current prices of market indicators). It specifies domestic indices and government bonds, distinguishing it from sibling tools like getPrices (stocks) and getExchangeRate.

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?

Explicitly states supported symbols come from a catalog of 8 types and that unsupported symbols return a 400 error. This guides when to use the tool. However, it does not explicitly contrast with other market indicator tools like getMarketIndicatorCandles.

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