업종별 종목 시세 조회

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

With no annotations provided, the description discloses key behaviors: sorting by stock code (종목코드순) and pagination limitation (first page only, max 100 stocks). It also references the Kiwoom API code (ka20002). It does not elaborate on error handling or auth, but for a read-only quote retrieval tool, the disclosed traits are valuable and beyond what a schema would provide.

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: two sentences covering purpose, sorting, pagination, and parameter guidance. It is front-loaded with the main purpose and avoids redundancy or filler. Every sentence contributes meaningful information.

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 list-query tool with no output schema, the description covers the essential aspects: what it returns (quotes), ordering, pagination, and how to specify the sector. It is sufficiently complete for an agent to select and invoke the tool correctly, even without an output schema.

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% for both parameters, so the baseline is 3. The description adds value by pointing out that sector_code can be sourced from get_market_index or a sector name, which is not in the schema. This cross-reference helps the agent understand how to construct a valid parameter value.

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+resource: '특정 업종에 속한 종목들의 시세를 조회합니다' (retrieves quotes for stocks belonging to a specific sector). This distinguishes it from sibling tools like get_sector_price (sector index) and get_sector_flow, making the purpose unambiguous.

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 gives clear context by noting that sector_code can be obtained from get_market_index or used directly as a sector name. It implies the tool is for sector constituent stocks, which differentiates it from index-level sector tools. However, it does not explicitly state when not to use this tool or name alternative tools.

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