fund_hk_fund_hist_em

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint, and openWorldHint, so the safety profile is covered. The description adds the upstream data source URL and the dependency on `fund_em_hk_rank` for the code parameter, which is helpful context, but it does not disclose rate limits, data freshness, or any deeper behavioral traits beyond what the annotations provide.

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 front-loaded with the tool's identity and includes structured :param and :return lines. It is efficient overall, though the bare URL and the restated return line add a little redundancy without much extra value.

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 two-parameter retrieval tool with no output schema, the description tells the agent what to pass and that the result is a pandas.DataFrame. It stops short of describing what columns or date coverage the historical NAV/dividend data includes, which would help an agent judge whether the result meets a given data need.

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 0%, so the description carries the full burden for both parameters. It successfully explains how to acquire `code` (via `ak.fund_em_hk_rank()`) and enumerates the two allowed values for `symbol`. The only minor gap is that the exact format or meaning of the code string is not specified beyond its acquisition path.

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 names the source (东方财富/天天基金网), the resource (香港基金), and the specific data variant (历史净值明细 or 分红送配详情), which is a clear verb+resource statement. It does not explicitly differentiate itself from the many sibling fund tools, but the resource is specific enough that an agent can identify it without opening the schema.

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?

It gives useful guidance for the `code` parameter by pointing to `ak.fund_em_hk_rank()` to obtain it, and it lists the two possible `symbol` values. However, it does not explain when to choose this tool over alternatives like `fund_hk_rank_em` or `fund_fh_rank_em`, nor does it clarify when to use 历史净值明细 versus 分红送配详情.

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