stock_hsgt_fund_min_em

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is fully covered. The description adds that the data is 分时 (intraday/minute-level) and returns a pandas.DataFrame, which is modest but real behavioral context. It does not describe refresh cadence, data range, or column layout.

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, source URL, and parameter are front-loaded with no filler. Sphinx-style :type/:rtype lines are boilerplate, and the title repeats the annotation title, but overall it stays tight.

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-parameter data-fetch tool with no output schema, the definition covers the data source, domain, granularity, and the parameter choices. It stops short of describing the returned minute-series fields or time coverage, leaving gaps an agent would otherwise need to guess.

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, yet the description supplies the valid choice set {"北向资金", "南向资金"} for the symbol parameter, which the schema omits. This is a meaningful addition, though it does not explain the default or the distinction between northbound and southbound.

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 source (东方财富-数据中心), the domain (沪深港通, Stock Connect) and the granularity (分时数据, intraday), which is a specific resource statement. However, it offers no differentiation from close siblings such as stock_hsgt_hist_em, stock_hsgt_fund_flow_summary_em, or stock_hsgt_hold_stock_em, so an agent cannot tell them apart from the text alone.

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 other HSGT or macro data tools. The single :param/:return line gives no context about selection, prerequisites, or alternatives.

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