stock_sector_fund_flow_rank

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true, so the safety profile is clear. The description adds the source URL (https://data.eastmoney.com/bkzj/hy.html) and return type, but does not disclose rate limits, authentication, or any data behavior beyond the annotations. No contradiction, but limited additional context.

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, with a clear header (title/URL), structured :param and :return sections. The duplicate title line matches the annotation but is not overly wasteful. It front-loads the source path and parameter definitions without extraneous text.

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 simple read-only tool with two optional parameters, the description provides parameter choices and a high-level return statement (pandas DataFrame of ranking data). However, it does not describe the DataFrame's columns or any nuances about the data (e.g., date handling, sorting), leaving some gaps given there is no output schema.

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 schema description coverage at 0%, the description fully compensates by enumerating exact choices for both parameters: indicator accepts {'今日', '5日', '10日'} and sector_type accepts {'行业资金流', '概念资金流', '地域资金流'}. This adds semantic meaning that the raw schema (just string type and defaults) lacks, making parameter selection unambiguous.

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 specifies the resource (sector capital flow) and the action (ranking) via the path '资金流向-板块资金流-排名' and the return '资金流排名数据'. It clearly indicates that this tool fetches sector fund flow ranking data. However, it does not explicitly differentiate from sibling tools like stock_sector_fund_flow_hist or stock_sector_fund_flow_summary, so it doesn't reach a 5.

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 no explicit guidance on when to use this tool versus alternatives. It only describes parameters and return value. The implied usage is for ranking data, but there is no when/when-not or alternative comparison, so it fails to direct an agent effectively.

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