stock_rank_cxsl_ths

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true, covering the safety profile. The description adds that the return is a pandas DataFrame and gives the source URL, which is useful context but does not disclose additional behavioral traits such as network dependency, data freshness, or output contents. This meets the baseline expected when annotations are present.

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 description is very brief, consisting of a title, a URL, and return type lines. It avoids unnecessary words and is easy to scan. However, the 'return: 持续缩量' line is somewhat redundant with the title, and a more structured sentence could improve clarity without adding bulk.

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?

Given the tool's simplicity (0 parameters, no output schema), the description provides the essential purpose and source, but it does not describe the DataFrame structure, columns, or the exact ranking criteria beyond the phrase '持续缩量'. Without an output schema, the description is expected to elaborate on return values; it only gives a terse label. This is adequate but leaves some gap for an agent seeking full understanding.

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?

The tool has zero parameters, and the schema reflects this with 100% coverage. The description does not need to explain parameters since there are none, and the baseline for no-parameter tools is 4. The description does not add any misleading parameter information.

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 description identifies the data source (同花顺-数据中心), the category (技术选股), and the specific indicator (持续缩量), along with a URL. It clearly indicates this tool provides a ranking list of stocks with continuous volume contraction, distinguishing it from sibling tools by suffix. However, it lacks an explicit verb like 'get' or 'fetch', relying on the tool name and context.

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?

The description does not provide any guidance on when to use this tool versus alternatives. Sibling tools cover other technical indicators (e.g., stock_rank_cxd_ths for a different strategy), but no differentiation or selection criteria are stated. Usage must be inferred solely from the tool name and the small descriptive phrase.

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