get_kosdaq_stock_daily

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

With no annotations, the description carries full behavioral disclosure burden. It only indicates a read operation ('조회') and specifies the date parameter, but does not mention return format, business day handling, or any limitations. This is insufficient for transparent 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 appropriately brief: one sentence plus an Args block. It is well-structured and front-loaded, though it omits some useful context that could be added without bloat.

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 tool has a single parameter, and an output schema exists, so return details are not needed. However, the description lacks context about what 'trading information' includes and does not explicitly mention that this is for stocks (vs. index or other KOSDAQ products), which is important given the many sibling tools.

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 input schema provides no description for basDd, so the description compensates by specifying the format '기준일자 (YYYYMMDD)'. This adds meaning beyond the schema, but the semantic meaning of 'base date' is not expanded further.

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 states '코스닥(KOSDAQ) 일별매매정보를 조회합니다' (retrieves KOSDAQ daily trading information), which is a specific verb and resource. It clearly identifies the market and frequency but does not explicitly distinguish from siblings like get_kosdaq_index_daily or get_kosdaq_stock_futures_daily; the name carries the 'stock' modifier.

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?

No guidance is provided about when to use this tool versus alternatives. The description only lists the parameter format and gives no context for selecting it over similar daily market tools.

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