get_kospi_index_daily

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

No annotations are provided, so the description itself must disclose behavior. It only states the operation is a query and the data is daily price info; it does not mention output format, pagination, date constraints, or any side effects. This is minimal but not contradictory.

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 one sentence plus a single parameter explanation, with no filler. It is front-loaded with the main purpose and concise.

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 the tool's simplicity (one parameter) and the existence of an output schema, the description covers the essential invocation details. However, it lacks any usage context or constraints, which is a minor gap for agents distinguishing among many similar 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 schema property basDd has no description (0% coverage), but the description's Args section adds meaning by specifying it is a base date (기준일자) with format YYYYMMDD. This compensates for the lack of schema description.

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 'KOSPI 시리즈 지수 일별시세정보를 조회합니다' (retrieves daily market info for KOSPI series index), specifying the action and resource. This distinguishes it from sibling tools like get_krx_index_daily and get_kosdaq_index_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 no guidance regarding when to use this tool versus the many sibling daily price tools. It does not mention alternatives, exclusions, or use cases, offering only a factual statement of function.

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