fund_graded_fund_info_em

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds the return type (pandas.DataFrame of historical NAV detail), which is genuinely useful given there is no output schema, but it says nothing about pagination, time range, or rate limits.

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 block is short but wastes space: the first line, the :return line, and the :rtype line all restate the same resource name, and the raw URL occupies prime position. It is neither bloated nor front-loaded with the information an agent actually needs.

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 one-parameter, no-output-schema tool this covers source, parameter meaning, and return type. It still omits whether the entire NAV history is returned or a bounded window, and how to choose this over the daily graded-fund sibling, leaving notable gaps.

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% for the single symbol parameter, so the description must compensate. It does explain that symbol is a 分级基金代码 and suggests a retrieval function, which adds meaning beyond the bare string/default in the schema, but the suggested source function appears incorrect and the expected code format (e.g. 150232) is never clarified.

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 exact dataset (分级基金净值-历史净值明细 from 东方财富/天天基金网), which is more specific than the bare tool name. However, it is essentially a restatement of the annotation title with no verb and no differentiation from the sibling fund_graded_fund_daily_em, so an agent cannot tell historical-detail from daily-quote without inference.

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 when-to-use, when-not-to-use, or alternative is stated. The only context offered is how to obtain the symbol value (via ak.fund_money_fund_daily_em()), which is parameter sourcing rather than usage guidance — and it points at a money-market-fund function rather than the graded-fund sibling, which is misleading.

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