get_konex_stock_base_info

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

With no annotations provided, the description carries the full burden of behavioral disclosure, yet it only restates the lookup action. It does not mention read-only nature, data source, authentication, rate limits, or potential errors, offering little transparency beyond the tool's name.

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 succinct and front-loaded with the primary purpose, followed by the parameter explanation. No extraneous words or repetition.

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?

With one required parameter and an output schema, the description is adequate for basic invocation. It lacks explicit guidance on valid date ranges or clarification of 'base info' vs. daily data, but the existence of sibling tools and the output schema mitigate these gaps.

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 schema provides no parameter descriptions (0% coverage), but the description compensates by fully explaining basDd as '기준일자' (base date) with the format YYYYMMDD. This gives the agent precise input requirements.

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 it retrieves KONEX stock basic information using the verb '조회' (retrieve) and the specific resource 'KONEX 종목기본정보'. It distinguishes itself from sibling daily price tools and other market base-info tools by market, but does not elaborate on what 'base info' includes.

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?

There is no guidance on when to use this tool versus alternatives such as get_kospi_stock_base_info or get_kosdaq_stock_base_info. The description does not mention conditions, prerequisites, or exclusions, leaving the agent to infer usage solely from the tool name.

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