stock_rank_lxxd_ths

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

Annotations already declare the tool as read-only, idempotent, and non-destructive. The description adds the return type (pandas DataFrame) and source URL, but does not disclose additional behavioral aspects like data freshness, network dependencies, or output structure beyond the type. No contradiction with 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 concise, consisting of a title-like Chinese label, a URL, and a short return type specification. Each piece of information serves a purpose, and the description is front-loaded with the key identifier.

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?

The tool is simple with no parameters and no output schema, but the description only states the return type and a vague content description ('连续下跌' - consecutive decline). It does not specify what columns or data the DataFrame contains, nor any caveats about the data. This is adequate for a basic tool but leaves gaps about the returned 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?

The tool has no parameters, as confirmed by the empty input schema. The description adds nothing about parameters because none exist; the baseline of 4 is appropriate given the vacuous schema coverage.

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 labels the tool as a ranking from 同花顺's data center for consecutively declining stocks, with a source URL and return type. It distinguishes itself from sibling rank tools via the specific label '连续下跌' (consecutive decline), though it lacks an explicit verb like 'fetches' or 'retrieves'.

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 explicit guidance on when to use this tool vs alternatives. It is merely a label with a URL and return type; usage is only implied by the name and title, with no mention of exclusions or alternatives.

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