get_market_indicators

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

Annotations already indicate read-only and non-destructive, and the description adds that it returns current prices (현재가), conveying point-in-time data. It also documents the exact supported symbol set, a behavioral constraint not present in the schema.

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 and well-structured, with purpose front-loaded in the first sentence, followed by usage guidance and parameter details. No redundant sentences.

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 one-parameter read-only tool with an output schema and annotations, this description covers purpose, scope, parameter format, and sibling differentiation. It is complete for effective selection and invocation.

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 schema provides zero description for the 'symbols' parameter, so the description compensates by explaining the comma-separated format and listing all 8 valid symbols. This fully documents parameter usage.

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 fetches current prices for domestic indices and government bond yields, using the specific verb '조회한다' (fetches). It distinguishes from sibling get_price by explicitly noting individual stock quotes should use that tool.

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?

It provides example queries for KOSPI and bond yields, making when-to-use explicit, and directly states that get_price should be used for individual stock quotes. It also limits scope to the 8 supported symbols, preventing misuse.

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