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

No annotations are provided, so the description carries the full burden of disclosing behavior. It does not state that this is a read-only lookup, any data limitations, date/market scope, or rate/authentication constraints, leaving the operation's behavioral profile mostly unspecified.

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 one short front-loaded sentence: the resource is named first, followed by a compact key-value legend for the parameter. There is no filler or repeated schema information.

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?

For a single-parameter tool with an output schema, the parameter semantics are complete enough to make a call. However, the lack of usage differentiation and any behavioral caveats leaves some context missing for an agent choosing among many sibling tools.

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 schema provides only a plain string 'type' with 0% description coverage and no enum, so the description is the sole source of meaning. It defines all three valid values with Chinese labels (institution 机构榜, hotmoney 游资榜, activeseat 活跃席位), fully compensating for the schema gap.

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 resource as the 龙虎榜 (Dragon-Tiger List) sub-list and enumerates its modes, so an agent can tell it is a categorized LHB lookup. It is clear, though it has no verb and does not explicitly contrast itself with sibling tools like ashare_hot.

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 type=... legend implies when to choose each variant (institution vs. hot money vs. active seats), but there is no explicit when-to-use or when-not-to-use guidance relative to the sibling ashare_* tools. An agent must infer applicability from the domain name 龙虎榜分榜.

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