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

No annotations are supplied, so the description carries the full burden, and it does substantial work: discloses that 龙虎榜 is 盘后数据, that an empty date resolves to the most recent appearance with the returned date authoritative, caps results at ~10 seats, states descending net-buy ordering, and flags 机构版专属 (a licensing/tier constraint). Minor gaps remain on error behavior and whether the 10-seat cap silently truncates.

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-loaded with the core purpose, then alternative routing, then caveats marked with ⭐ and ⚠️ — a good scannable hierarchy. It loses a point for mild redundancy, repeating the ~10 seat limit twice and listing field names that the output schema already exposes.

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 2-parameter read tool with an output schema, the description supplies everything an agent needs: what it returns, ordering, the seat cap, the tie-in date default, the institutional-tier restriction, and the sibling routing rule. No material gap remains.

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 coverage is 100%, so both parameters (code formats, date default) are already fully documented in the schema, which sets the baseline at 3. The description restates the empty-date behavior rather than adding new syntax or format semantics, so it earns no premium over 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?

States a specific verb+resource in both languages: 单票的营业部买卖席位明细 with is_youzi flag, and enumerates returned fields. It explicitly distinguishes itself from the sibling ashare_lhb (榜单 vs 单票明细), so an agent can separate the two without opening either 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 literal user-question triggers ('今天龙虎榜是谁买的/哪个营业部/是不是游资/沪股通买了多少') and names the alternative tool with the exact condition that selects it ('问「谁买的」用本工具，问「今天哪类资金活跃」用 ashare_lhb'). Exclusions and routing are both present.

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