stock_rank_ljqd_ths

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds that the return type is pandas.DataFrame and provides the source URL, which is useful but does not disclose behavior such as data completeness, freshness, or any peculiarities of the ranking list.

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 concise, containing only the titled source, URL, return label, and return type. Every element contributes, with no redundancy or filler. The docstring format is well-structured.

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?

Given the tool's simplicity (no parameters, clear annotations, and a specific data type), the description adequately states what it returns and where the data comes from. It lacks column details, but for a basic ranking list with a recognizable Chinese stock-market indicator, this is sufficient.

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 is empty with 100% coverage. Per guidelines, the baseline for 0 params is 4, and no parameter descriptions are required.

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 tool as providing data on '量价齐跌' (volume and price both falling) from 同花顺's data center technical stock selection, which distinguishes it from sibling rank tools. It includes a URL for the source and states the return type, making the purpose understandable, though it lacks an explicit action verb like 'fetch' or 'list'.

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 description provides no guidance on when to use this tool versus the many sibling stock_rank_*_ths tools. It only states what it returns without mentioning any context, prerequisites, or exclusions.

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