stock_rank_lxsz_ths

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering safety. The description adds the source URL and a return type of pandas.DataFrame, but does not disclose any additional behavioral traits such as data freshness, row limits, or the exact meaning of '连续上涨' (e.g., number of days). This is slightly above minimal but still lacks meaningful behavioral context beyond the annotations.

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 extremely short, front-loaded with the title, and includes only a URL and return type docstring. It wastes no words and is appropriate for a zero-parameter data retrieval tool. However, the URL line could be considered slightly arbitrary and the overall structure is minimal.

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?

There is no output schema, so the description must explain return values. It only says '连续上涨' (consecutive gains) without specifying the columns (e.g., code, name, days of rise), sorting, or data scope. The lack of detail about the DataFrame structure makes it incomplete for an agent to predict what data will be returned. Annotations provide safety context but not output semantics.

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 tool has zero parameters, and the schema correctly reflects this with an empty properties object. Since there are no parameters to explain, the baseline of 4 applies. The description adds no parameter information but is not required to.

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 explicitly identify the tool as the THS Data Center page for '连续上涨' (consecutive gains), along with a direct URL. This clearly indicates it fetches a ranking of stocks with consecutive rises, distinguishing it from sibling rank tools by the specific lxsz (连涨) indicator. However, it does not explicitly state the action verb like 'list' or 'get', and relies heavily on the name/title to convey the resource.

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 guidance on when to use this tool versus alternatives. The description provides no context on use cases, prerequisites, or comparison with siblings such as stock_rank_cxd_ths or stock_rank_lxxd_ths. It simply states the data source and return type without explaining scenarios where this ranking is appropriate.

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