获取加密货币历史价格

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

With no annotations, the description must carry behavioral disclosure. It states the data includes price, volume, and technical indicators, which gives some insight. However, it does not clarify the nature of technical indicators, return ordering, pagination, rate limits, or that the tool is read-only. The description is not contradictory, but it lacks richness.

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 a single, focused sentence that front-loads the core purpose. It wastes no words and provides the essential information in a compact form.

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?

For a simple historical data fetcher with a comprehensive schema, the description gives a reasonable overview but lacks details about return structure, ordering, or usage scenarios. Since there is no output schema, the description could be more explicit about what the data looks like. It is adequate but leaves gaps for an agent unfamiliar with OKX K-line conventions.

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 description coverage is 100%, so the parameters are already well-documented with formats for bar, limit, and instId. The description adds little beyond what the schema offers, only indicating that data includes price, volume, and indicators. Baseline 3 is appropriate because the schema does the heavy lifting.

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 explicitly states the tool retrieves OKX cryptocurrency historical K-line data including price, volume, and technical indicators. The verb '获取' (get) and specific resource 'OKX加密货币的历史K线数据' are clear, and it distinguishes itself from stock-focused siblings and other OKX metrics tools like okx_loan_ratios and okx_taker_volume.

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?

No guidance is provided on when to use this tool versus alternatives. It does not mention that this is the tool for OHLCV data as opposed to other OKX data tools, nor does it reference any sibling tools or exclusions. The context is implied by the name and description but no explicit comparison is given.

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