종목 매수 유의사항 조회

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

Annotations already declare readOnlyHint and idempotentHint, so the safety profile is clear. The description adds substantial context by enumerating all warning types (LIQUIDATION_TRADING, OVERHEATED, etc.), return fields (exchange, startDate, endDate), and the behavior of returning an empty array when no warnings exist.

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 well-structured with a clear front-loaded purpose and separate Args/Returns sections. However, it repeats the parameter description from the schema, which is redundant, though the detailed Returns section justifies the length.

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?

Despite lacking an output schema, the description thoroughly explains the return structure, including fields and all possible warningType enum values. It also clarifies symbol formats for KRX and US, making the tool fully understandable for a simple 1-parameter operation.

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 description includes an Args section that exactly mirrors the schema's description for the symbol parameter, providing no additional meaning beyond the schema. With schema coverage at 100%, the baseline score of 3 applies.

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 '특정 종목의 투자 유의사항 및 경고 정보를 조회합니다' (retrieve investment cautions and warnings for a specific stock), using a specific verb and resource. It is distinct from sibling tools that handle market data, orders, or accounts, making its 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 explains what the tool does but does not explicitly state when to use it versus alternatives. Usage is implied by its function (e.g., checking warnings before trading), but there is no explicit 'when-to-use' guidance or mention of alternative tools.

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