fund_etf_fund_info_em

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true, so the safety profile is covered. The description adds the data source URL and return type but discloses no additional behavioral traits such as date range handling, pagination, or error behavior. It provides marginal value beyond the 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 reasonably concise and structured as a docstring. However, it redundantly repeats the title phrase in the first line and the return line, and includes a URL that could be seen as extra. It is not excessively verbose, but the duplication could be trimmed.

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?

There is no output schema, and the description only states the return type is pandas.DataFrame without describing columns or data structure. While the title implies historical NAV data, an agent would benefit from knowing the exact columns or any nuances like date inclusivity. The description is adequate but not exhaustive for a data retrieval tool.

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 0% description coverage, so the docstring fully compensates by defining all three parameters (fund, start_date, end_date). It adds meaning, especially for 'fund' by referencing how to obtain the code, but the date parameters are only described as 'start/end time' without specifying format (though defaults imply YYYYMMDD).

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: fetching historical NAV details for on-exchange trading funds from Eastmoney. It specifies the resource ('场内交易基金-历史净值明细') and uses a specific verb ('获取' implied), distinguishing it from siblings like spot price tools.

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 implies a prerequisite by noting the fund code can be obtained via fund_etf_fund_daily_em, but it does not explicitly state when to use this tool versus alternatives (e.g., fund_etf_hist_em for price data). Usage context is implied, not explicitly articulated.

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