get_flow

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

No annotations are provided, so the description must carry the full burden. It does mention the data limitation, but it does not disclose whether the tool is read-only, has any side effects, error handling, or permission requirements, leaving behavioral aspects unclear.

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 line breaks but is somewhat verbose, including a warning and usage examples. It could be slightly more concise while retaining key information.

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?

The description covers the main purpose, limitations, and alternative tool, which is sufficient for a simple read operation. However, it does not explain the output format or any error conditions, though an output schema exists.

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?

Both parameters are described clearly: code (6-digit stock code) and days (number of days, default 20). The description covers the schema parameters fully, despite the schema itself lacking 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 that the tool fetches investor supply-demand data (institutional and foreign net trading stock counts) for a single stock, distinguishing it from the batch version. It also specifies the source limitation (no individual net trading).

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 instructs to use get_flow_batch when there are 2 or more stocks, and provides example user queries ('외국인 수급', '기관 순매수') to indicate when this tool is appropriate.

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