stock_hk_hot_rank_detail_realtime_em

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

Annotations already establish a safe read-only, idempotent operation (readOnlyHint=true, destructiveHint=false). The description adds that it returns a pandas DataFrame and provides the data source URL, but offers no additional behavioral context like rate limits, pagination, or authentication requirements. 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 compact and follows a docstring-like structure with a title, URL, parameter, and return type. It is front-loaded with the purpose. The minor inconsistency between the described symbol format and the schema default slightly detracts from clarity.

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 low complexity (one parameter, no output schema), the description covers the basic source and return type. However, '实时变动' is vague and does not explain the DataFrame's columns or structure, leaving some ambiguity about what the data contains.

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 description adds crucial meaning to the 'symbol' parameter by stating it must include a market representation (e.g., HK_00700), which is not evident from the schema alone. The default of '00700' in the schema is inconsistent with this format, but the description still provides valuable guidance.

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 states it fetches real-time changes for an individual stock's popularity ranking from East Money, with a URL example (HK_00700) providing concrete scope. However, it does not explicitly differentiate this from sibling tools like stock_hk_hot_rank_detail_em, instead relying on the 'realtime' in 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 alternatives, nor any mention of scenarios, prerequisites, or exclusions. The description simply defines the data source and parameter without helping the agent decide when to invoke it.

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