ETF 기간 수익률 조회

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

No annotations provided, so description carries responsibility. It discloses read-only nature (조회) and data source (키움 ka40001). Could mention output format details, but no contradictory information present.

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?

Two sentences, front-loaded with purpose, then parameter guidance. No wasted words.

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?

Covers purpose and parameters well with cross-references, but lacks description of output structure. Since no output schema exists, the description should indicate what the returned data contains (e.g., period returns and index returns).

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 coverage is 100%, but description adds meaning: explains default benchmark_index_code, cross-references get_market_index for codes, and advises using search_stock for unknown stock codes. This goes beyond bare schema descriptions.

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 period returns for ETFs alongside benchmark index returns. It uses specific verbs (조회) and resources (ETF 기간별 수익률) and distinguishes from siblings like get_etf_info and get_market_index.

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?

Provides explicit guidance: how to find stock codes via search_stock, how to get index codes via get_market_index, and the default benchmark index code. Lacks explicit when-not-to-use or alternatives, but context is sufficient for correct invocation.

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