option_lhb_em

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true and destructiveHint=false, so the safety and idempotency profile is covered. The description adds only the source URL; it says nothing about the external dependency being a scraped web page, rate limits, data latency, or the fact that results are a mutable snapshot of a live ranking.

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 resource and symbol/indicator choices are front-loaded and useful, but the ':type symbol: str' style lines and the lone URL are noise that duplicates the schema's type information and adds nothing to invocation. It is compact but not fully economical.

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, the description is the only place return information could live, yet it says only ':return: 期权龙虎榜单 / :rtype: pandas.DataFrame' without naming a single column or dimension. All parameters are optional with defaults, so basic invocation is possible, but an agent cannot anticipate the shape of the result.

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%, so the description must carry the parameter burden and largely does: it enumerates the three valid symbol codes and the four indicator values, which the bare schema omits. The gap is trade_date, documented only as '交易日期' with no format guidance beyond the default value shown in the schema.

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 names a specific resource — the Eastmoney option Dragon-Tiger (龙虎榜) leaderboard dataset — and anchors it to a source URL, which is far more concrete than the tool name alone. It stops short of explicitly differentiating itself from the many sibling option_* analysis tools (option_premium_analysis_em, option_risk_analysis_em, option_value_analysis_em), so an agent must infer the distinction from the resource label.

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 statement of when to select this tool over alternatives, no prerequisites, and no exclusions. The description only lists parameters and a source, leaving the agent to guess how it relates to the dense cluster of sibling option and futures tools.

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