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

Annotations already declare readOnly/idempotent/non-destructive/openWorld, so the safety profile is covered; the description adds provenance (SZSE ShowReport CATALOGID=1804_gptj_merge_after), keyless access, and result ordering (turnover descending). It does not discuss freshness beyond what the schema says, but the source and ordering notes are real value-adds.

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 statement of what the tool returns, followed by the vendor-metric exclusion and query examples. The bilingual parentheticals and the 'A 农林牧渔 … T 综合 etc.' enumeration run long, but they carry real information for matching Chinese-language intent.

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 only two optional params, no output schema, and annotations covering safety, the description compensates well by naming the returned fields and the sort order. Minor gaps: no note on row-count limits (top caps at 50 per schema) or latency/caching behavior of the upstream exchange catalog.

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% and both parameters (top, date) are fully documented in the schema, including the default-today and nearest-session fallback behavior. The description adds no per-parameter semantics beyond restating that output is sorted by turnover, so the baseline 3 applies.

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: SZSE-official per-industry turnover ranking for Chinese A-shares, and enumerates exactly what each row contains (turnover, share volume, company count, market caps, weighted P/E). It also explicitly disambiguates from the similarly-seeming vendor '主力资金净流入' metric, so an agent can separate it from other flow-type tools without opening the 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 queries ('今天A股行业板块成交额排名', 'which sectors traded the most today') and an explicit when-NOT-to-use clause ruling out large-order net inflow questions. The only mild gap is that no sibling tool is named as the alternative for those excluded questions.

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