get_qhkc_fund_bs

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

The description adds the available time window and the output structure (symbol_df and long_short_df), which goes beyond the annotations. It also provides sample data to illustrate the return format. There is no contradiction with the read-only, idempotent, and open-world annotations.

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 bloated with a large sample output (over 50 lines), while the actual guidance is minimal. The critical information (what, when, parameters) is mixed with huge data tables, making it hard to scan quickly.

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 description does explain the return value (pandas DataFrame with symbol_df and long_short_df) and provides sample data, which is helpful given the lack of an output schema. However, the parameter descriptions are inadequate, and it doesn't clarify the exact date format or handling of out-of-range dates. For a simple tool, this is middling.

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 input schema has no descriptions (0% coverage), so the description must clarify parameters. It lists 'url: 网址' and 'date: 中文名称', but the latter is vague and likely erroneous ('Chinese name' instead of 'date'). The date format is only inferable from the sample output, which is insufficient.

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 names the resource ('净持仓分布' = net position distribution) and indicates this is a data retrieval function for that specific dataset from Qihuo Kechacha. The specific resource is named, but it does not explicitly differentiate from sibling tools like get_qhkc_fund_position or get_qhkc_fund_money_change.

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 choose this tool over alternatives. It mentions an available date range (2016-10-10 to 2019-09-30) which acts as a constraint, but there is no explicit recommendation, exclusion, or comparison with sibling tools.

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