외국인 보유 추이 조회

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

No annotations provided, but description discloses default ordering (latest first), default number of days (15), and adjustable range via limit (up to 50). Adequate for a read-only query tool without performance or side-effect details.

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 front-loaded with key functionality and parameters. No wasted words; every sentence adds value.

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?

No output schema, but description lists specific data fields provided. With only 2 simple parameters and no nested objects, the description is reasonably complete for an agent to understand inputs and outputs.

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% for both parameters. Description adds meaningful context: explains default and maximum for limit, and implies daily latest ordering. This enhances understanding beyond the schema definitions.

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 the tool queries daily foreign holding trends for a specific stock, listing specific data fields like closing price, volume, net change. This distinguishes it from siblings like get_stock_price or get_short_selling.

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 usage for historical foreign holding data by stock, and mentions default 15 days with adjustable limit. No explicit alternatives or when-not-to-use, but siblings cover different data types so context is clear.

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