stock_individual_fund_flow_rank

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering safety. The description adds that it returns a pandas DataFrame and specifies the return type, but does not disclose additional behavioral traits such as data freshness, pagination, or rate limits. Some value added but not rich.

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 compact and well-structured, containing a source label, URL, parameter documentation, and return type in a standard docstring format. It is efficient without wasted words, though it mixes Chinese and English but remains readable.

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 tool with no output schema, the description provides the source URL, parameter choices, and return type, which is adequate. However, it could improve by explicitly stating that it covers individual stock fund flow rankings and distinguishing it from sector/industry fund flow rank 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?

The input schema lacks any description for the 'indicator' parameter and no enums are defined. The description compensates by listing the valid choices and indicating that they are period options, thereby providing meaning beyond the schema.

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 clearly indicates the resource (East Money data center fund flow ranking) and the action (return ranking), though it lacks an explicit imperative verb. It is distinct from siblings by implying rank-focused fund flow data, but does not explicitly state 'individual stock' in the description.

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?

The description provides context by listing indicator choices ('今日', '3日', '5日', '10日') and the data source URL, implying when to use it. However, it does not explicitly state alternatives or when not to use this tool, leaving usage guidance implicit.

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