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

No annotations are provided, so the description carries the full burden and does: response shape per item ({code, ok, data} or error), requested/returned/failed counts, A-share-only scope with ok:false fallback for HK/US, rate-limit behavior, billing by actually-returned stocks with refunds on throttling, and the paid-tier requirement (Pro ¥99+). This is unusually complete disclosure for a mutation-free but quota-sensitive tool.

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 core purpose and the sibling differentiation, then organized under ⚠️ headers for limits/usage/return/billing. It is dense and long, with some repetition (the 10/20-stock cap appears in both the limits block and the codes guidance), but given the tool's quota and billing complexity nearly every sentence earns its place.

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?

Even though an output schema exists (so return values needn't be explained), the description still tells the agent what comes back and how failures are represented, plus the tier gate, quota math, and market scope. Nothing needed to call this correctly is missing.

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%, so the baseline is 3, but the description adds real meaning beyond it: comma-separated codes with bare 6-digit support, periods defaulting to 4 with max 12 and descending newest-first ordering, and the coupling constraint that stock count × periods consumes quota. Only minor duplication with the schema keeps it from a 5.

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 verb and resource: batch financial statements (income/balance/cashflow) for multiple stocks, with per-stock success marking. It explicitly distinguishes itself from sibling ashare_finance, noting that /v1/finance returns a flat 3-table blob where you cannot tell which stock failed. An agent can pick correctly without opening either schema.

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 phrasing (users asking about revenue/net profit/ROE/debt ratio/operating cash flow for several stocks), names the alternative (ashare_finance) and the condition that selects it (multi-stock, needs per-stock ok/error). Adds hard limits (Pro 10 / unlimited-tier 20, stocks × periods ≤ 40), worked examples of where quotas break, and the batching strategy with interval guidance.

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