stock_main_fund_flow

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description adds only the upstream data source URL and adds nothing about freshness, pagination, or result scope, so it contributes little behavioral context beyond the structured fields.

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 is front-loaded in the first line, but the block is a raw docstring dump with redundant :type and :rtype lines that restate what is already implied. It is short enough not to be bloated but not tightly edited.

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, read-only ranking tool with no output schema, the description covers the source, the parameter choices, and the return shape (pandas.DataFrame of the ranking). It is minimally adequate but does not clarify result granularity or how the ranking is ordered/sized.

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% and the schema has no enum, so the description's full choice list for symbol ({"全部股票", "沪深A股", "沪市A股", "科创板", "深市A股", "创业板", "沪市B股", "深市B股"}) is a genuine and necessary addition. It compensates for the schema gap, though it does not explain what each market segment means for the returned ranking.

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 first line identifies the resource (main-fund net-inflow ranking from East Money's data center) and the URL confirms the source. However, it largely restates the tool name and title and offers no differentiation from siblings such as stock_individual_fund_flow, stock_market_fund_flow, or stock_sector_fund_flow_rank, which an agent would need in order to pick the right one.

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 the many fund-flow siblings, no prerequisites, and no exclusions. The only guidance is the default symbol value, which is usage-adjacent but not a when-to-use rule.

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