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 it does disclose a lot: paid tiers (Pro ¥99+), per-call caps of 200/300, billing by actually returned rows, ~1 year of history, A-share-only scope with ok:false for HK/US/sector codes, and non-trading-day fallback. It stops short of describing failure modes like rate limits or partial-timeout behavior, so it is strong but not exhaustive.

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?

Purpose and the sibling comparison are front-loaded, and every section carries distinct information (comparison, performance rationale, usage, return shape, scope, limits, pricing). It is nonetheless heavy with emoji warning markers and bold emphasis, which adds visual noise to an already long block.

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?

With no annotations and an output schema present, the description still covers scope limits, tier caps, pricing, date fallback and the requested/returned/failed envelope. An agent has everything it needs to decide and invoke 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%, so both parameters are already documented, giving a baseline of 3. The description does add meaning the schema lacks — bare 6-digit codes are accepted, and date applies globally to all codes with automatic fallback to the last trading day.

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 opening line names a specific verb and resource (batch chip distribution) and enumerates the exact metrics returned (profit ratio, average cost, 90%/70% concentration) plus the per-stock success flag. It explicitly distinguishes itself from sibling ashare_chip by explaining the N×8N diagonal-matrix defect of the single-code endpoint.

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 concrete user phrasings that should trigger this tool ('are these stocks' chips concentrated / how much is trapped / average cost'), states the alternative (ashare_chip) and why it fails for multiple codes, and notes that single-code queries are still acceptable here. When-to-use, when-not-to-use and the fallback option are all present.

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