kis_search_stock

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

No annotations are provided. The description adds that master data is updated once per day and the first call triggers a download taking a few seconds, which is a useful behavioral trait. However, it does not disclose other aspects like rate limits, read-only nature, or error scenarios.

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 concise sentences. The main action is front-loaded, followed by scope and a note on data freshness. It earns its space with no redundancy, though a single sentence could have sufficed.

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 search tool with no output schema, the description covers essential context: what you can search, market scope, and data update behavior. However, it does not specify the output format (e.g., list of stocks with codes/names), which might be inferred but is not explicit.

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 for query, limit, and markets. The description adds minimal extra semantics (market scope, data refresh) but mostly repeats what the schema already conveys. Baseline 3 is appropriate as the schema does the heavy lifting.

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 states 'Search stocks by stock code or stock name' and specifies support for domestic (KOSPI/KOSDAQ) and overseas (US, Hong Kong, Japan, etc.) markets. This clearly defines the verb-search and resource-stocks, and distinguishes from sibling tools like kis_get_domestic_stock_price or kis_place_domestic_order which focus on other operations.

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 implies usage for finding stocks before performing other operations, but does not explicitly state when to use it versus alternative tools. No 'when-not' guidance or direct mention of sibling tools is provided. However, the purpose is clearly distinct from siblings.

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