fund_report_stock_cninfo

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 only the report-period constraint and that the return is a pandas.DataFrame, which is minor added context rather than rich behavioral disclosure. No mention of pagination, rate limits, or data coverage/caveats.

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 resource is front-loaded, but the body is a raw docstring dump including a source URL and low-value ':type date: str' / ':rtype: pandas.DataFrame' lines that restate what the schema implies. It is short enough overall but has some redundant scaffolding.

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 single-parameter, no-output-schema fetch tool this is minimally adequate: the agent knows the input format and that it returns a DataFrame of fund heavy holdings. However, the actual returned columns and any data caveats are undocumented, so an agent cannot fully anticipate the response shape.

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 carries the burden and does it reasonably: it names the parameter (报告时间 / report time) and gives the accepted period format via the choices {"XXXX0331", "XXXX0630", "XXXX0930", "XXXX1231"}, which is not encoded as an enum in the schema. This meaningfully compensates for the schema gap, though it does not explain the default or the quarter-end semantics explicitly.

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 Chinese header identifies the resource (巨潮资讯 fund-report heavy-holdings stocks, '基金重仓股'), so an agent can tell it returns fund top-holding data. However, the first line is essentially the same string as the annotation title, and there is no differentiation from close siblings like fund_report_industry_allocation_cninfo or fund_report_asset_allocation_cninfo. It states a resource but not in a way that clearly distinguishes this tool from its family.

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 when-to-use guidance, no conditions, and no named alternatives. The description only lists source metadata and parameter/return types, leaving the agent to infer that this is a date-keyed fund holdings snapshot. No exclusions or preferred-use statements are provided.

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