stock_fund_flow_big_deal

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so safety profile is covered. The description adds the source URL and return type (pandas.DataFrame), but does not disclose any behavioral details such as data freshness, pagination, or latency. It provides minimal value beyond annotations.

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 description is very brief and contains no fluff, but it is under-specified rather than efficiently concise. It repeats the title instead of providing meaningful structure or front-loaded actionable information.

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?

The description fails to explain what '大单追踪' (big deal tracking) actually contains, what fields are in the DataFrame, or how this tool differs from similar fund flow tools. With no output schema and minimal description, an agent would not know the data's structure or use case, making it incomplete.

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?

The tool has zero parameters with 100% schema coverage (vacuously). The baseline for zero parameters is 4, and the description does not need to explain parameters since there are none.

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 is essentially a repetition of the title '同花顺-数据中心-资金流向-大单追踪' with a URL and return type. It lacks an explicit verb (e.g., 'fetch', 'list') and merely names the resource, making it a tautology rather than a clear statement of purpose.

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?

No guidance is provided on when to use this tool versus alternatives. With numerous sibling tools covering different fund flow aspects (e.g., individual, industry, concept), the description offers no context for selection, exclusions, or prerequisites.

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