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

With no annotations provided, the description carries the full burden and does so well: it discloses a hard cap of 15 codes with the consequence that the data source silently drops the rest (20 codes → 6 returned), that each code reports its own 'ok', that fields differ by market (A-share has targetPrice, HK has none and uses *Forecast fields), that it is read-only, and that it requires a paid tier (¥99+).

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 resource name and purpose, then triggers, then warnings — every sentence earns its place. The heavy bold/symbol formatting and mixed-language phrasing make it slightly harder to parse than plain prose, but there is no filler.

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?

An output schema exists, so return values need not be explained. Combined with the market-dependent field warning, the batch-size truncation behavior, and the subscription-tier requirement, an agent has everything needed to call it correctly and interpret partial results.

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% and the single param is documented there, so the baseline is 3. The description adds real value beyond the schema by explaining that each code is processed individually and what happens when the ≤15 limit is exceeded — a behavioral consequence the schema does not convey.

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 resource (卖方一致预期 / analyst consensus) and enumerates exactly what it returns: target price plus forward estimates (EPS, revenue, net profit, forecast PE/PB/PS, coverage count). This is clearly distinguishable from nearby siblings like ashare_rating (ratings) or ashare_finance (reported financials).

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 concrete trigger phrases for when to call it ('机构怎么看/目标价多少/明年利润预测/一致预期'). It does not name an alternative sibling or state when to prefer ashare_rating or ashare_finance instead, so the routing guidance is clear but not exhaustive.

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