get_krx_index_daily

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It merely says 'retrieve', implying a read-only operation, but offers no details about output format, limitations, or any special behavior. This is minimal and lacks transparency.

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 extremely concise, consisting of a single sentence followed by an Args section. Every word earns its place with no fluff or repetition, appropriate for a one-parameter 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 has an output schema, so the description need not explain return values. However, it lacks context about what 'KRX series' refers to and provides no caveats or background. It is minimally viable but not comprehensive.

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 has 0% description coverage for basDd, so the description must compensate. It does so by explaining 'basDd: 기준일자 (YYYYMMDD)', adding meaning and format. This is helpful, though it could be more explicit about the parameter's role.

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 the tool retrieves daily price information for KRX series indices ('KRX 시리즈 지수 일별시세정보를 조회합니다'), using a specific verb and resource. However, it does not explicitly differentiate from sibling index tools like KOSPI/KOSDAQ/bond/derivatives, though the 'KRX series' scope is somewhat distinct.

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 the many sibling tools. The description only explains the basic function and does not mention alternatives, prerequisites, or typical usage scenarios.

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