fund_open_fund_info_em

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint, covering the safety profile. The description adds useful context: the data source (东方财富网-天天基金网), the URL, and the return type (pandas.DataFrame). However, it does not disclose any additional behavioral traits such as pagination, rate limits, or specifics about what data the returned DataFrame contains, so it provides only modest added value beyond 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 compact, with the purpose and source URL front-loaded, followed by clear parameter docstrings and return type. Each line serves a purpose; no fluff. The only minor issue is that the title line is repeated verbatim in the annotations' title field, but that doesn't dilute the description itself.

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?

With good annotations and no output schema, the description provides enough for basic usage but has clear gaps: the set of valid indicator values is absent, and the returned DataFrame structure is not described. It explains the source and period options but leaves the most important parameter (indicator) vague, making the tool's capabilities less predictable than they could be.

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 coverage is 0%, so the description must carry parameter meaning. It explains symbol (基金代码 with a way to obtain all codes) and period (with an explicit choice list). However, indicator is only described as '需要获取的指标' (the indicator to fetch), which is tautological and gives no list of valid values or examples. This leaves a key parameter under-specified.

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 fetches open-end fund net value data from 天天基金网 (East Money), with a specific URL and resource. It describes the action as returning data for a specified fund and indicator. However, it doesn't explicitly distinguish itself from closely related sibling tools like fund_open_fund_daily_em or fund_open_fund_rank_em, so it misses full sibling differentiation.

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 alternative fund data tools. It only mentions that the symbol can be obtained by calling ak.fund_open_fund_daily_em(), which is a prerequisite rather than a usage guideline. There are no exclusions or alternative tool references.

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