stock_rank_cxfl_ths

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is clear. The description adds the source URL and return type, but does not disclose any additional behaviors like data frequency, granularity, or pagination. With annotations carrying the main burden, this is acceptable but not enriching.

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 very short and structured with a title, URL, and return annotations, making it compact. However, it repeats '持续放量' multiple times (in the title and return statement), causing slight redundancy. It could be more informative without added length.

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 should at least sketch what the returned DataFrame contains (e.g., stock codes, names, volume statistics). It only says '持续放量', which is vague and leaves the agent uncertain about the exact output structure or what criteria define the ranking.

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, so the schema fully covers the input. The description repeats the return type but adds no parameter semantics, which is appropriate for a parameterless tool. Baseline for 0 params is 4.

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 identifies the resource as THS Data Center technical stock selection for '持续放量' (continuous volume increase), which clarifies the cryptic 'cxfl' in the tool name. However, it lacks an explicit verb like 'fetch' or 'list' and does not detail what qualifies as continuous volume, so it is more of a label than a full purpose statement.

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 is given on when to use this tool versus its many sibling tools such as stock_rank_cxd_ths or stock_rank_cxg_ths. The description simply states the ranking name without any context for selection or exclusions.

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