A股龙虎榜统计

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

No annotations are provided, so the description must disclose behavioral traits. It only states the basic purpose without mentioning data freshness, rate limits, side effects, or any constraints. The agent does not know if the data is cached, how often it updates, or what happens on errors.

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 a single concise sentence that conveys the core purpose. It is not overly verbose, though it could benefit from slightly more structure (e.g., separating purpose from data source mention).

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 output schema and only a brief description, the agent lacks information about the return data structure. The tool returns statistics, but the description does not explain what fields (e.g., stock names, counts, percentages) are included, leaving the agent uncertain about how to use the output.

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%, and both parameters (days, limit) have descriptive comments specifying allowed values and ranges. The description adds no extra parameter information beyond the schema, so it meets the baseline for adequate semantic support.

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 title and description clearly indicate the tool retrieves A-share market dragon and tiger list (LHB) individual stock statistics. It specifies the market (Shanghai, Shenzhen) and mentions multi-data-source support. This distinguishes it from sibling tools that cover other stock metrics.

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?

No explicit guidance on when to use this tool versus alternatives. The name and description imply it's for LHB statistics, but there is no context about when to prefer it over other stock tools or what scenarios it suits (e.g., historical vs real-time).

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