업종 현재가 조회

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

With no annotations, the description carries full burden. It lists the returned data components (index price, open/high/low/close, volume, etc.), which is helpful. However, it does not explicitly state that this is a read-only operation or mention any behavioral traits like permissions or rate limits. The description is largely transparent but could be stronger.

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 two sentences: the first states the purpose and lists data components concisely, the second explains the parameter. Every word adds value, and the critical information is front-loaded.

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, the description adequately explains the return data (list of components). The single parameter is fully explained with source and examples. For a simple query tool, it is sufficiently complete, though an explicit mention of the output structure would improve it.

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 already describes sector_code with pattern and description. The description adds significant value by explaining that the code comes from get_market_index and providing concrete examples (001, 002, 101, 201). This helps the agent understand the parameter's source and allowed values.

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 current price details of sector indices, listing specific data components (index, open/high/low/close, volume, etc.). It distinguishes from sibling tools like get_market_index (which lists indices) and get_stock_price (which is for stocks).

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 states that sector_code comes from get_market_index, providing a clear prerequisite. However, it does not explicitly state when to use this tool versus alternatives or when not to use it, though the purpose is well-defined.

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