stock_hk_index_spot_sina

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive, so the safety profile is covered. The description usefully adds a rate-limit/IP-ban warning and retry guidance plus the return type (pandas.DataFrame), which are genuine behavioral facts not present in the structured fields.

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?

Purpose is front-loaded, but the block is cluttered with a bare documentation URL and docstring artifacts (':return:', ':rtype:') that duplicate information. The rate-limit warning earns its place; the URL and formatter tags are mostly noise.

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, no-output-schema read tool, the description covers what is returned (all HK index real-time quotes as a DataFrame), the data source, and the throttling caveat. Little else is needed for correct invocation.

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 takes zero parameters, so per the rubric the baseline is 4; there is nothing for the description to disambiguate and it introduces no misleading parameter 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 states a specific source (新浪财经), resource (港股指数), and scope (所有指数的实时行情数据), so an agent knows it returns real-time HK index quotes. It does not, however, explicitly distinguish itself from close siblings like stock_hk_index_spot_em or stock_hk_index_daily_sina beyond the embedded source 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?

Usage is only implied: '实时行情' signals snapshot data rather than history, and the IP-ban/10-minute-retry note gives operating context, but there is no explicit statement of when to pick this over the EM-sourced sibling or the daily-history sibling.

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