get_hk_historical_k_data

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It states the tool returns 'Markdown格式的K线数据表格' (K-line data table in Markdown format), which is useful output information. However, it doesn't disclose important behavioral aspects like whether there are rate limits, authentication requirements, data freshness, error conditions, or pagination for large date ranges. For a data retrieval tool with no annotations, this leaves significant gaps.

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 well-structured and appropriately concise. It starts with the core purpose, then lists parameters with clear explanations, and ends with return format. Each sentence earns its place, and there's no redundant information. The bilingual format (Chinese purpose, English parameter names) is slightly unconventional but doesn't hinder clarity.

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 moderate complexity (5 parameters, no annotations, but has output schema), the description is minimally adequate. It covers the basic purpose and parameters well, and the output schema existence means it doesn't need to detail return values. However, for a financial data tool with many sibling alternatives and no behavioral annotations, it should provide more context about data sources, limitations, or typical use cases to be truly complete.

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 description adds substantial semantic value beyond the input schema, which has 0% description coverage. It explains that 'code' is a Hong Kong stock code with an example ('hk.00700' for Tencent), clarifies date format ('YYYY-MM-DD'), indicates 'frequency' defaults to 'd' (daily), and mentions 'fields' is an optional field list. This compensates well for the schema's lack of descriptions, though it doesn't specify possible frequency values or field options.

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's purpose: '获取港股历史K线数据' (Get Hong Kong stock historical K-line data). It specifies the resource (Hong Kong stocks) and action (get historical K-line data), making the purpose unambiguous. However, it doesn't explicitly differentiate from sibling tools like 'get_historical_k_data' (which appears to be for non-HK stocks) or 'get_hk_stock_realtime_data' (real-time vs historical), so it doesn't reach the highest score.

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 on when to use this tool versus alternatives. With many sibling tools available (e.g., 'get_historical_k_data' for non-HK stocks, 'get_hk_stock_realtime_data' for real-time data, 'get_hk_stock_basic_info' for basic info), there's no indication of when this specific historical K-line tool is appropriate versus other data retrieval tools. The description assumes the user already knows when to fetch historical K-line data.

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