stock_report_fund_hold_detail

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds the data source (Eastmoney data center) and an example URL, but nothing about latency, data freshness, or return contents beyond 'pandas.DataFrame'. No contradiction with 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?

It is a raw Sphinx docstring dump (the :param/:type/:return/:rtype scaffolding) rather than agent-optimized prose. The core signal is front-loaded, but the type-annotation boilerplate adds length without adding meaning.

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 2-parameter read-only tool with annotations covering the safety profile, it is adequate: both params are explained and the return type is stated. However, the date-format mismatch with the default and the absence of any note on returned columns or coverage leave minor 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%, so the description must carry the burden, and it does: symbol is defined as fund code and date as the report publish date with quarter-end format examples. Minor inconsistency: the stated dashed format (xxxx-03-31) conflicts with the schema default '20220331', which could confuse an agent.

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 a specific resource: Eastmoney fund holding detail (基金持仓-明细). The verb is implicit ('get') but the data source path and URL make the target unambiguous. It does not explicitly distinguish itself from the closely named sibling stock_report_fund_hold, so it falls short of a 5.

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?

There is no guidance on when to use this tool versus alternatives such as stock_report_fund_hold, fund_portfolio_hold_em, or fund_hold_structure_em. The description is purely a parameter/data-source listing with no contextual routing.

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