종목 검색 (이름→코드)

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

With no annotations, the description carries full burden. It discloses first-call delay (몇 초 걸림), 12-hour cache, and underlying API (키움 ka10099). It does not discuss rate limits or error handling, but for a simple search tool this is sufficient. Could mention that partial matches may return multiple candidates.

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 cover purpose, usage guidance, and performance characteristics. No redundant words. The core function is stated first, followed by crucial usage advice. Excellent brevity.

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?

Covers purpose, usage order, caching, and latency. Does not describe output format (e.g., JSON structure) but implies it returns the stock code. Since no output schema exists, a brief note on output would improve completeness. However, for a simple search tool, the description is nearly complete.

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 has 100% description coverage for the single 'query' parameter. The description enriches by confirming partial matching ('부분 일치') and giving concrete examples (삼성전자, KODEX 미국, 6자리 코드). This adds value beyond the schema's generic description.

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 searches for KOSPI/KOSDAQ stocks (including ETFs/ETNs) by partial name or 6-digit code to find the stock code. The title '종목 검색 (이름→코드)' reinforces the name-to-code conversion. This purpose distinguishes it from sibling tools like get_stock_price or get_stock_chart that require a pre-known stock code.

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 directs to use this tool first when the stock code is unknown ('다른 tool에 넘길 종목코드를 모를 때 먼저 사용하세요'). It also mentions the first-call latency and 12-hour cache, setting expectations and preventing premature retries.

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