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

With no annotations, the description still discloses the key behavioral traits: full payload is ~1 MB and will consume large amounts of context, so limit/pagination is mandatory, and '-' field values mean the data source lacks that attribute rather than a failed fetch. It does not state data freshness/as-of time or result ordering, which keeps it short of a 5 for an unannotated 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 capability, then the routing rule, then the cost warning, then the data-semantics caveat — each block earns its place. It is slightly long with three stacked ⚠️ markers, but nothing is filler.

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?

An output schema exists, so return-shape explanation is unnecessary, yet the description still names the fields. Combined with the payload-size warning, the sibling routing rule and the '-' sentinel semantics, an agent has everything needed to call this correctly without surprises.

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 schema already documents limit, market, offset and industry; baseline is 3. The description adds the practical rationale (why to set limit, using market to narrow before paging) but gives no extra syntax or format detail beyond the schema.

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+resource (全市场股票清单 / 一次拿全 A 股约 5576 只) and enumerates the returned fields (代码/名称/市场/上市日期/行业/板块/发行价/注册资本). It explicitly contrasts itself with the sibling ashare_search, 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?

Names the triggering user intents (『所有上市公司有哪些 / 全部股票代码 / 某行业有哪些公司』, building a universe), and states the exclusion rule against ashare_search (search requires a keyword; this tool must not be given one). It also prescribes narrowing via market + limit when only codes are needed.

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