stock_rank_ljqs_ths

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

Annotations already declare readOnly, idempotent, non-destructive. The description adds only the return type (pandas.DataFrame) and URL, but no behavioral context like pagination limits, data freshness, or potential network failures. With annotations covering safety, still minimal added value.

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?

Extremely concise: three lines including title, URL, and return type. No filler, well-structured docstring format.

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 simple no-param data fetch, the description gives source and return type, but lacks details about DataFrame columns, data update frequency, and exact contents beyond '量价齐升'. Without an output schema, this leaves the agent guessing about the data structure.

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 has zero parameters, so description need not explain params. It implicitly indicates no inputs are required, which is consistent. Baseline of 4 for no-param tools.

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 clearly identifies the source (THS Data Center) and specific screening criterion (量价齐升, volume-price increase), with a URL and return type. It distinguishes from sibling rank tools by specifying this is the ljqs (量价齐升) ranking, though it lacks an explicit verb like 'fetch' or 'return'.

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?

No guidance on when to use this tool vs other stock_rank_* tools. Sibling tools like stock_rank_cxg_ths or stock_rank_xstp_ths exist, but the description doesn't differentiate use cases. No exclusions or context.

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