get_stock_base_info

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

No annotations provided, so description carries full burden. Describes API call per basDd and filtering by codeList, but does not mention idempotency or authentication. However, the behavior is transparent enough for an agent to understand usage.

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?

Three concise sentences with no wasted words. Front-loaded with purpose, then filtering rule, then API behavior. Ideal length.

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 enumerates key return fields (한글 종목명, 영문 종목명, 상장일, 주식종류, 액면가, 상장주식수). Explains filtering and API call behavior. Fully sufficient for a data retrieval tool given complexity and sibling context.

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 describes all parameters fully (100% coverage), so description adds marginal value. It reinforces that codeList filters results and explains API call frequency per basDd, which is helpful beyond 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?

Description clearly states it provides base info (name, listing date, etc.) for stocks on given base dates, filtered by market and code list. Unambiguously distinguishes from sibling tools which deal with corporation codes, disclosures, financial statements, etc.

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 notes that only stocks in codeList are extracted and that each basDd triggers an API call, implying rate limit considerations. Does not explicitly state when not to use or compare to siblings, but context is sufficient.

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