stock_report_fund_hold

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered by structured data. The description adds the return type ('pandas.DataFrame') which is useful given there is no output schema, but says nothing about returned columns, pagination, or source 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?

Content is compact and front-loaded with the source name, but the raw URL and Sphinx-style :param:/:type:/:rtype: boilerplate are noise for an agent and could be trimmed without losing 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 two-parameter read-only data tool with no output schema, coverage is adequate: both params and the return type are documented. It stops short of describing the returned data shape or any source reliability caveats, which an agent would find useful for a scraped Eastmoney endpoint.

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?

With 0% schema description coverage, the description does the heavy lifting: it enumerates the accepted symbol values (基金持仓, QFII持仓, 社保持仓, 券商持仓, 保险持仓, 信托持仓) and explains the date field as a report publication date with quarter-end examples. Minor flaw: the stated date format 'xxxx-03-31' contradicts the dashless default '20210331', which could mislead.

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 source and resource concretely: '东方财富网-数据中心-主力数据-基金持仓', so an agent understands it retrieves fund-holding (main-capital) data from Eastmoney. It is clear but does not distinguish itself from the closely named sibling stock_report_fund_hold_detail, leaving the boundary implicit.

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 statement of when to use this tool versus alternatives, no prerequisites, and no indication of when the symbol categories apply. The reader must infer usage purely from the parameter list.

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