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

No annotations are present, so the description carries the burden of behavioral disclosure. It adds useful context that the tool is free and requires no API Key, and it clarifies the market scope (A-share/US/ETF). It does not describe ranking recency or sorting semantics, but the read-only nature is reasonably apparent from the hot-list framing.

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 very compact: it front-loads the resource and use case in the first clause, then adds only the relevant no-key note. There is no filler or repetition.

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 tool with one optional parameter and an output schema, the description covers the market scope, user intent, and authentication requirements. The only notable gap is that `limit` is left undocumented, though its name and default mitigate the ambiguity.

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?

The only parameter, `limit`, has zero schema description coverage and the description never mentions it. The English name and default value of 30 make it partially self-explanatory, but with 0% coverage the description should have compensated and did not.

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 names a specific resource: a hot-search list for A-shares, US stocks, and ETFs, and connects it to a concrete user intent ('什么股票热门/大家在看什么'). It lacks an explicit verb like 'returns' or 'lists', but the noun phrase plus usage intent is clear and distinguishes it from the sibling ashare_* tools.

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?

The description gives a direct trigger condition: use this when users ask which stocks are hot or what everyone is watching. It gives clear context for when to invoke the tool, though it does not explicitly name alternatives or state when not to use it.

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