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

There are no annotations, so the description carries the full burden: it discloses read-only semantics ('只读查询'), the paid-tier prerequisite (专业版 ¥99+), and a call-shape quirk where comma-separated codes yield one segment per code that must be retrieved via `tables`. That multi-code behavior is important operational context not expressed anywhere in the schema.

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 description is front-loaded with what is returned, then when to use it, then the critical constraints, using bolding for emphasis. It is dense but every sentence carries information; the HK/US-only restriction is repeated in two places, which is slightly redundant but justified by the misleading tool name.

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 no further explanation. With one required parameter fully documented, a clear market restriction, a named fallback sibling, and the paywall plus multi-segment behavior disclosed, an agent has everything needed to invoke this correctly.

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 code format is already documented, so the baseline is 3. The description adds value beyond the schema by explaining the multi-code behavior ('逗号多只，每只一段（用 `tables` 取全部段）'), which affects how the parameter should be passed and how results should be read.

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 uses a specific verb and resources: it returns analyst target prices (mean/high/low), rating distribution with coverage counts, and monthly rating trend. It also distinguishes itself from the sibling `ashare_consensus` by scoping to HK/US only, something neither title nor name conveys (the name misleadingly says 'ashare').

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?

Explicit triggers are given ('机构目标价多少/评级怎么样/多少家覆盖'), an explicit exclusion is stated twice in bold (A-shares are not supported; use `ashare_consensus`), and the input format (`hk00700`/`usAAPL`) is exemplified. An agent has no ambiguity about when to pick this tool versus alternatives.

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