stock_fund_flow_individual

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

The annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered elsewhere. The description adds source provenance (the 同花顺 URL) and the return type (pandas.DataFrame), but discloses nothing about pagination, column shape or data latency.

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 purpose line is front-loaded and the docstring-style lines are terse, but the raw URL and the boilerplate :rtype: line add limited value for an agent. It is neither wasteful nor notably efficient.

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-optional-parameter, annotation-rich tool this is close to sufficient: the source, parameter values and return type are all present. It still omits sibling selection rationale and any indication of the DataFrame contents, which for a finance data pull would be useful.

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 and no enum in the schema, the description is the only place that documents the parameter: it lists all five accepted values (即时, 3日排行, 5日排行, 10日排行, 20日排行), which is exactly the information an agent needs to invoke the tool correctly.

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 (同花顺-数据中心), the category (资金流向/fund flow) and the scope (个股/individual stocks), which is enough to identify the resource. However, it is a noun phrase with no verb and makes no attempt to distinguish itself from near-identical siblings such as stock_individual_fund_flow, stock_fund_flow_concept or stock_fund_flow_industry.

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 call this tool versus the many other fund-flow tools, nor any prerequisite or context. The only usage-adjacent content is the enumerated symbol values, which is parameter documentation rather than routing guidance.

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