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

With no annotations, the description carries the full burden and it delivers two non-obvious behavioral facts: results are isolated per API Key, and the CRUD watchlist calls do not consume data quota (cost implication). It stops short of describing ordering, empty-list behavior, or error cases, but the key operational traits are disclosed.

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?

A single front-loaded line with a bolded purpose tag, followed by scoping and cost clauses. Every clause (isolation, return payload, quota) carries distinct information with no repetition of structured fields.

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 zero parameters, an existing output schema (which documents the returned list and symbols), and no annotations, the description supplies what the schema cannot: per-key isolation and quota behavior. Only the empty/error case is left unaddressed, which is minor for a listing call.

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 tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline for a no-param tool applies. The description correctly adds only scope context (API-Key isolation) rather than inventing filter semantics.

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 verb+resource is explicit ('查自选股' = query watchlist) and the return payload is stated ('返回列表和标的'), which distinguishes it from sibling read tool ashare_watchlist_quotes that would return prices. It doesn't name the add/remove/quotes siblings directly, so differentiation is inferred from naming rather than stated.

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?

Usage is only implied: the 'CRUD 不扣数据次数' clause positions it as the read member of a watchlist CRUD family, hinting that add/remove are the write counterparts. There is no explicit 'use this when X, use ashare_watchlist_quotes when Y' routing, so an agent must infer the boundary itself.

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