stock_lhb_ggtj_sina

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds only the source URL and an rtype, disclosing nothing about what the statistics contain, update cadence, or return shape beyond 'pandas.DataFrame'. Little value beyond structured data.

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 definition is short, which is good, but it is a raw pasted docstring with a bare URL and a redundant ':return:' line that merely restates the tool title. Slightly wasteful and not front-loaded with any actionable guidance.

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 one-parameter read-only tool with no output schema, the parameter documentation is complete. However, in such a dense sibling namespace the omission of any disambiguation or usage context leaves a real gap an agent would need filled.

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 carries the full burden for the single parameter. It does so well, enumerating each symbol value and its meaning ('5'=最近5天, '10'=最近10天, '30'=最近30天, '60'=最近60天), which the schema leaves entirely undocumented. Minor deduction because the default of '5' is not restated.

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 resource, 龙虎榜-个股上榜统计 (Dragon-Tiger list per-stock listing statistics), which is concrete enough for an agent to understand the data returned. However, it makes no attempt to distinguish itself from the many closely-named siblings such as stock_lhb_yytj_sina (brokerage statistics), stock_lhb_jgzz_sina, or stock_lhb_detail_daily_sina.

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 or when-not-to-use statement, and no alternative is named. In a namespace crowded with lhb tools (stock_lhb_yytj_sina, stock_lhb_jgmmtj_em, stock_lhb_stock_statistic_em, etc.), the agent is left to guess which one produces 'individual stock listing statistics'.

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