stock_rank_xzjp_ths

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false. The description adds the source URL and return type, but no additional behavioral details such as rate limits or data freshness. It does not contradict 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 very short (three lines) and front-loaded with the title, but the first line simply repeats the tool's Chinese title, which is redundant with the 'title' annotation. Still, it's concise with no filler.

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 no-parameter, read-only data retrieval tool with no output schema, the description provides the source URL and the general output type. However, it does not explain what '险资举牌' data contains (e.g., columns, stock codes, time coverage), leaving some ambiguity for an agent deciding if this tool is relevant.

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 input schema has zero parameters, so the baseline is 4. The description correctly does not attempt to document parameters; no param-related guidance is needed.

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 data source (同花顺-数据中心-技术选股-险资举牌) and return type (pandas.DataFrame), but lacks an explicit verb like 'get' or 'list'. It mostly restates the tool's name/title, making it somewhat tautological. It doesn't distinguish itself from sibling stock_rank_*_ths tools beyond the name.

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 other stock_rank_*_ths tools or alternatives. No when-to-use or when-not-to-use information is provided.

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