종목 현재가 조회

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

No annotations are provided, so the description carries the burden. It discloses limitations (no dividend yield/dividend data because Kiwoom REST API lacks the TR) and what additional data is included (industry, listing date, trading halt/supervision warning flags). This is good transparency about coverage and edge cases, though it doesn't mention pagination, response format, or potential delays.

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 clearly states the purpose and data returned, the second notes a specific limitation and provides navigation guidance. No wasted words, front-loaded with the key action and resource.

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 single-parameter query tool with no output schema, this description is complete: it specifies input format, what data to expect, what's excluded, and additional status flags. The only minor gap is not stating the response format (JSON shape), but that's often acceptable. Given the tool's simplicity and sibling context, it's well-rounded.

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 covers the single parameter (stock_code) with a pattern and example. The description reinforces the format (6자리 종목코드) and adds that it's domestic stocks/ETFs, plus the search_stock fallback. Since schema coverage is 100% and there's only one parameter, the description adds meaningful context without redundancy.

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, change rate, volume, and basic indicators (PER, EPS, PBR, market cap) for a 6-digit Korean stock/ETF code. It explicitly distinguishes itself from search_stock and other stock-related siblings by focusing on current price snapshot, not charts, quotes, or sector data.

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 provides clear context: it's for querying current price and indicators by stock code, and includes a when-not-to-use note (dividend info not available via Kiwoom REST API) and a cross-reference to search_stock when only the name is known. It doesn't explicitly enumerate alternatives for other use cases, but the sibling list and clarity make usage reasonably clear.

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