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

No annotations are provided, so the description must carry the behavioral burden. It does well by enumerating exactly what data is returned (capital-flow windows and rankings, dragon-tiger reasons/branches, block trades, margin), though it does not state that the tool is read-only or side-effect free.

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?

Front-loads the core capability, then adds the usage trigger and two clearly marked exclusions. Every sentence earns its place, and the warning markers make the routing constraints scannable.

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?

Given an output schema exists, there is no need to explain return values. The description covers what data is included and where the tool sits relative to alternatives, which is complete for a single-stock, single-parameter query tool.

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?

There is one parameter with 100% schema coverage, and the schema already documents the code format (e.g. sh600667). The description adds no syntax or format detail beyond the schema, so the baseline of 3 is appropriate.

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?

States a specific verb/resource: stock-level trading data including main capital flow, dragon-tiger list details, block trades, and margin trading. It also explicitly distinguishes itself from siblings ashare_lhb (market-wide lists) and ashare_fund_batch (multiple stocks), so an agent can route without opening a schema.

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?

Gives an explicit when-to-use trigger ('用户问某只股票的主力资金/机构动向'), plus two explicit exclusions with named alternatives: market-wide lists go to ashare_lhb, multi-stock scans go to ashare_fund_batch. Nothing is left to inference.

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