fund_value_estimation_em

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the read-only nature is established. The description adds the data source URL and return type (DataFrame), which is useful but does not elaborate on pagination, rate limits, or data scope beyond 'recent'. It adds minimal behavioral context 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 structured with a title, URL, parameter documentation, and return type. It is reasonably concise, though the URL adds length and could be considered non-essential. The key information is front-loaded with the Chinese title, and the docstring format is easy to parse.

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?

Given the tool has only one optional parameter and no output schema, the description provides sufficient information for an agent to invoke it: the param choices, return type, and data source. It could have mentioned default behavior or data sorting, but for a simple read-only estimation tool, it is largely complete.

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 description includes a complete docstring listing all valid values for 'symbol' (全部, 股票型, 混合型, 债券型, 指数型, QDII, ETF联接, LOF, 场内交易基金). This significantly exceeds the input schema, which only provides type and default but no enum or explanation. The parameter semantics are fully documented in the description.

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 identifies the resource as '东方财富网-数据中心-净值估算' (East Money Net Value Estimation) and states it returns '近期净值估算数据' as a pandas DataFrame. This clearly indicates a data retrieval tool for estimated fund values, though it lacks an explicit verb like 'get' or 'fetch'. It somewhat distinguishes from siblings by its specific focus on net value estimation, but many similar fund data tools exist.

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 tools, nor does it mention exclusions or prerequisites. There is no mention of alternatives or specific use cases, leaving the agent without contextual selection help.

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