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

With no annotations, the description carries the full burden and does well: it discloses per-item success/failure semantics, hard caps (200 professional / 250 institutional), that billing is per actually-returned stock, the paid-tier requirement, and that non-A-share codes return ok:false rather than wrong data. It stops short of describing pagination/rate-limit behavior or what happens on a partially invalid code list.

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 bolding front-loads purpose well, but the description is a wall of repeated ⚠️ blocks with emoji, and the size cap appears twice (in 上限 and again in the parameter description and 付费工具 line). The speed benchmark is persuasive but sprawling; it could be compressed without losing information.

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 one-parameter batch tool with an output schema and no annotations, this covers everything an agent needs: what it returns, per-item error semantics, units (手/万元/亿元/股/百分数), market scope, size limits, and cost implications. Output schema means return shape needn't be fully spelled out, and it is anyway.

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; the description adds genuinely new meaning beyond the schema by stating that bare 6-digit codes are accepted in addition to prefixed sh/sz/bj codes, and repeats the per-tier caps as a calling constraint. Format examples and failure behavior for foreign codes are clarified.

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?

Opens with a specific verb+resource: batch full-field profiles for multiple stocks, listing the 35+ field groups covered. It explicitly contrasts with the sibling ashare_snapshot ('本工具一次给多只，ashare_snapshot 只查一只'), so an agent can route 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 user-phrasing triggers ('这几只的估值/市值/市盈率/是不是涨停'), names the single-stock alternative and the batch quote alternative, and states a when-NOT-to-use case: HK/US codes belong to ashare_quote because the field layout differs. Nothing is left to inference.

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