ChLhbData

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

No annotations are provided, so the description carries the full behavioral burden. It confirms the tool returns data but discloses nothing about permissions, rate limits, return shape, or whether the date is a single trading day—behaviors an agent would need for a market-data 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?

Very short and front-loaded, with the domain term stated first. The bilingual repetition is somewhat redundant but justified for a Chinese-market tool, and no sentence is wasted.

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 values need not be described. For a single-parameter read tool the description is minimally adequate, but it leaves the usage context and behavioral profile largely unaddressed.

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 0%, but the description partially compensates by specifying the date format as YYYYMMDD. However, it adds no semantics about what the date selects (single day vs range) or any constraints, so coverage remains incomplete.

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 states a specific verb and resource—fetching 龙虎榜 (Dragon-Tiger list) top-traded stock data—using a well-defined domain term. It is clearer than a vague 'get data' tool, but it does not explicitly distinguish itself from related siblings like ChLimitUpDown or ChDdxStockData.

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?

There is no when-to-use guidance, no prerequisites, and no mention of alternative tools. The only context is the argument format, which tells the agent nothing about when this tool is the right choice over its many siblings.

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