stock_individual_fund_flow

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

Annotations already declare readOnly, idempotent, non-destructive and openWorld, so the safety profile is covered. The description adds little beyond that - it notes the source site and that the return is a pandas.DataFrame of recent data, but no rate limits, auth needs, or column semantics.

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 short, but the docstring boilerplate (:param/:type/:return/:rtype) plus the bare URL adds some non-actionable material. Purpose is front-loaded, which is good, but the format is a raw Python docstring rather than agent-oriented prose.

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?

With no output schema, two simple non-mutating parameters, and safety fully covered by annotations, the description is minimally adequate. It still omits return contents and, more importantly, any distinction from the many sibling fund-flow tools.

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 parameter burden, and it does: stock is identified as the stock code, and market is documented with its valid values (sh/sz/bj for the three exchanges). That is meaningful added meaning, though no code-format example is given.

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 a clear source+resource pair (东方财富网 数据中心 - 个股资金流向), so an agent knows this returns individual-stock fund-flow data. However, it gives no differentiation from near-duplicate siblings such as stock_fund_flow_individual or stock_individual_fund_flow_rank, leaving the agent to guess which fund-flow variant to pick.

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, when-not-to-use, or alternative guidance. Given the density of fund-flow siblings in the toolset, this is a real gap: nothing tells the agent to prefer this over a market-wide or rank-style flow tool.

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