테마 그룹 조회

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

No annotations provided, so description carries full burden. It discloses default sorting by change rate and that limit is ignored when stock_code is used. However, does not mention data freshness, caching, authentication needs, or performance characteristics, leaving some gaps.

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 sentences in Korean (translated to English) cover all key points without redundancy. Could be more structured with bullet points, but is efficient and easy to parse.

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 hints at return fields (theme name, stock count, change rate, etc.) which aids agent understanding. References sibling tool for deeper details. For a simple 2-param tool, it provides sufficient 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?

Schema coverage is 100%, baseline 3. Description adds value by explaining that limit controls display count (default 30, max 100, in change rate order) and is ignored when stock_code is used. Also clarifies stock_code is a 6-digit pattern and its purpose.

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 a list of Kiwoom theme groups with specific fields (theme name, stock count, change rate, etc.) and distinguishes two modes: default top themes by change rate, or filtering by stock_code. It also references the sibling tool get_theme_stocks for constituent stocks, avoiding confusion.

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?

Provides explicit guidance: use for viewing theme groups or finding themes for a stock via stock_code. Recommends get_theme_stocks for constituent stocks of a specific theme. Lacks explicit when-not-to-use scenarios but is clear enough.

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