투자자별 매매동향 조회

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

No annotations provided, so the description carries the full burden. It explains the tool shows period totals and daily details, and mentions unit options. It is a read-only operation but doesn't describe pagination or limits, which is acceptable for this type of tool.

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 concise sentences with no wasted words. It includes the prerequisite (use search_stock if needed) and clearly states what the tool returns.

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 the tool has 4 parameters with full schema descriptions, and no output schema, the description adequately explains what is returned (period totals and daily details). It is fairly complete for the complexity of this tool.

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%, baseline 3. The description adds meaning to parameters: 'unit: amount(금액, 백만원, 기본)/quantity(수량, 주)' clarifies the enum values, and dates have default explanations. This provides useful context beyond the schema's 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?

The description clearly states the tool queries investor buying trends (개인/외국인/기관 순매수) for a stock, specifying it shows period totals and daily details. It also differentiates from sibling tools like search_stock.

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?

Explicitly advises to use search_stock if the stock code is unknown, providing a clear alternative. The description tells when to use this tool (for investor trend) and indirectly when not to use it (if you don't have the stock code).

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