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

With no annotations available, the description carries the behavioral burden well: it discloses read-only behavior, intraday rolling refresh cadence, free/anonymous 5-minute refresh limits, anonymous 5-symbol limit, array-shaped return data, and field naming quirks such as turnover. This is substantial context beyond 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 definition is front-loaded and information-dense, but it is long and repetitive: the multi-symbol warning about ashare_quote_batch appears in two consecutive blocks. Emojis and bold warnings add emphasis but also bulk.

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 the tool's complexity, output schema availability, and the many sibling alternatives, the description is complete enough for correct invocation. It covers purpose, alternatives, data shape, refresh tiers, anonymous limits, and index symbol edge cases.

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 description coverage is 100%, so the baseline is 3, but the description adds useful semantics: code accepts comma-separated symbols, multi-symbol use is discouraged in favor of batch, and specific US index symbols like usDJI/usIXIC/usINX are documented.

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 states a specific verb and resource: real-time quote snapshot for A-shares, HK, and US stocks, with a precise 8-field scope. It explicitly distinguishes itself from ashare_snapshot, ashare_kline, ashare_orderbook, and ashare_quote_batch.

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?

It gives explicit when-to-use guidance ('用户问某股票现在多少钱/什么价') and when-not-to-use guidance by naming alternatives: ashare_snapshot for valuation, ashare_kline for historical trends, ashare_orderbook for order book, and ashare_quote_batch for multiple symbols.

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