테마 그룹 조회

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

No annotations provided, so description carries the burden. It explains default sorting, the effect of stock_code filtering, and that limit is ignored when searching by stock. However, does not mention response format or data freshness, though field list is given.

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?

Two efficient sentences in Korean, front-loading the main purpose, then adding usage details and an alternative. No unnecessary words.

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 2 parameters, no output schema, and sibling tools, the description covers purpose, parameter behavior, and alternative tool. Lists return fields but lacks explicit format details. Sufficient for agents.

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 clear descriptions. Description adds context beyond schema by explaining default behavior and that limit is ignored with stock_code, moving beyond baseline 3.

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?

Description clearly states it retrieves Kiwoom theme group list with specific fields (테마명, 종목수, 등락률, etc.), distinguishing from sibling get_theme_stocks which retrieves constituent 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?

Explicitly describes default behavior (showing top themes by change rate) and alternative use with stock_code to search for themes containing a specific stock. Directly points to get_theme_stocks for constituent stocks, providing an alternative.

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