stock_hot_rank_em

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

Annotations already declare read-only, idempotent, open-world, and non-destructive behavior. The description adds the data source URL and return type (pandas.DataFrame), but no additional behavioral context such as rate limits, pagination, or column specifics. This is acceptable but not rich.

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 compact, consisting of a title, URL, and return type. It is not verbose, though the phrase '人气榜' appears twice and the structure is a bit repetitive. Overall, it is efficient for a no-parameter tool.

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 read-only tool with no output schema, the description should clarify the return contents. It indicates a DataFrame of popularity rankings and provides the source URL, but it does not describe expected fields (e.g., stock code, rank, popularity score). This leaves some ambiguity for the agent.

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 description does not need to compensate for schema gaps. The baseline of 4 applies, and the description correctly limits itself to the return type without adding irrelevant parameter information.

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 names the resource ('个股人气榜' – individual stock popularity ranking) and provides a source URL, but it lacks a clear verb and is essentially a title. It does not differentiate from sibling rank tools like stock_hot_rank_detail_em or stock_hot_rank_latest_em.

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, what it should be used for, or when to prefer an alternative. It solely states what it is without any contextual usage direction.

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