대차거래 추이 조회

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

No annotations are provided, so the description carries full burden. It discloses the data granularity (daily), default period (30 days), and behavior when stock_code is omitted (market aggregate). While it doesn't mention rate limits or pagination, it sufficiently covers the tool's basic behavior.

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 three concise sentences, front-loading the main purpose and then providing parameter defaults and a sibling reference. Every sentence adds value with no repetition or filler.

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 no annotations, 100% schema coverage, and no output schema, the description covers the essential aspects: purpose, parameters with defaults, a sibling alternative, and the data source. It is sufficiently complete for an agent to use the tool correctly.

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. The description adds significant value by explaining the default values for from_date and to_date (30 days ago to today) and the effect of omitting stock_code (market aggregate). This goes beyond the schema's pattern 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 retrieves daily stock lending trends, specifying the data fields (contracts, repayment, balance) and the API source. It distinguishes between querying a specific stock and the entire market, making the 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 explicitly tells users to refer to the sibling tool 'get_short_selling' for short selling flow, providing a clear alternative. It also explains the default date range and how to customize it, offering good context on when to use the tool.

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