stock_fund_flow_concept

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and non-destructive, so safety is covered. Beyond that the description adds nothing: it does not disclose that data comes from a scraped 同花顺 endpoint (reliability/freshness risk), whether there is rate limiting, or whether the ranking is cumulative vs point-in-time. Given the open-world scrape, this context would have been valuable.

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 body is a raw docstring dump: a bare URL on its own line, then Sphinx :param/:type/:return/:rtype lines. The URL is unstructured noise for an agent, and key info (what the tool does) is absent while formatting boilerplate is present.

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 one-optional-param read-only fetch with no output schema, the enum enumeration and stated return type (pandas.DataFrame of concept fund flow) are the essentials and they are present. Still missing is any indication of what columns to expect or how this differs from the many sibling fund-flow tools, so it is minimally viable rather than complete.

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%, but the description enumerates the exact choice set for symbol (即时/3日排行/5日排行/10日排行/20日排行), which materially compensates for the empty schema. It does not explain what '即时' means versus the ranked windows, but the enum lift alone earns baseline-plus.

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 states the source (同花顺-数据中心-资金流向-概念资金流) and names concept fund flow as the returned data, so the resource is identifiable. However it never states a verb or what the tool actually does (fetch/retrieve), and it does not differentiate itself from close siblings like stock_fund_flow_industry or stock_concept_fund_flow_hist, so it's vague rather than specific.

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 on when to use this versus industry fund flow, individual fund flow, or hist variants. The only hint is the parameter's time-window choices, which imply ranking-style queries but are not framed as usage conditions.

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