get_kosdaq_stock_options_daily

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

With no annotations, the description carries the full burden for behavioral disclosure. It states the operation is a read-only '조회' (retrieval), which implies no side effects. However, it does not mention anything about authentication, rate limits, pagination, or error behavior. For a simple data retrieval tool, the core behavior is disclosed, but additional context is missing.

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 concise and well-structured. It opens with a clear purpose sentence and includes a minimal Args block for the parameter. No unnecessary information, and all sentences contribute to understanding the tool.

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 is simple with one parameter and an output schema, so the description does not need to explain return values. The description covers the tool's scope (KOSDAQ stock options daily data) and the parameter format. It is complete for the tool's simplicity, though it could mention that the data is for a single date or that it is read-only, but these are reasonably implied.

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 only the parameter name 'basDd' with a title, giving no semantic meaning. The description compensates by explicitly defining basDd as '기준일자 (YYYYMMDD)' (base date, format YYYYMMDD). This fully explains the parameter's meaning and format, adding significant value beyond the schema.

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 a specific verb '조회합니다' (retrieves) and a specific resource '주식옵션(코스닥) 일별매매정보' (KOSDAQ stock options daily trading info). This clearly distinguishes it from sibling tools like get_kospi_stock_options_daily and get_options_daily.

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 provides clear context: it is for KOSDAQ stock options daily trading data. The name and description make the intended use obvious, though it does not explicitly mention alternatives or exclusions. The context is sufficient for an agent to select this tool when KOSDAQ stock options data is needed.

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