VI 발동 종목 조회

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

No annotations provided. The description is adequate for a read-only query tool, but does not explicitly state it's non-destructive, nor mention any permissions, rate limits, or side effects. Carries reasonable burden but lacks full behavioral context.

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?

Description is relatively concise and front-loaded with core purpose. Parameter details are appended logically. A minor point: could be slightly more streamlined by separating parameter info into a list, but overall efficient.

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 all 5 parameters are optional and there is no output schema, the description covers parameter meanings and implicitly describes return data (price, deviation, times). Sufficient for a targeted query tool; no nested objects or complex output to explain.

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%, so baseline is 3. Description adds value by explaining each parameter's options (market: all/kospi/kosdaq, direction: all/up/down, vi_type: all/static/dynamic) and the effect of stock_code. This goes beyond schema descriptions.

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?

Description clearly states it queries stocks with VI triggered today, with specific details (price, deviation, etc.). Well-differentiated from sibling tools, which cover different domains (account, holdings, market 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?

Description implies use for VI-related queries but lacks explicit guidance on when to use vs. alternatives. No exclusions or context about when not to use this tool. Sibling tools are thematically different, so differentiation is partially implicit.

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