stock_zh_kcb_spot

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true. The description adds a valuable behavioral warning that frequent scraping can lead to IP blocking, which is useful context beyond the annotations. It also provides the data source URL, adding transparency about origin.

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 brief and front-loaded with the key purpose. The URL and warning are useful additions without excessive verbosity, though the mix of Chinese text and the :return:/:rtype: lines could be more structured for an English-speaking agent.

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 parameterless, read-only tool, the description covers the essential aspects: source (Sina Finance), data type (real-time KCB quotes), return format (DataFrame), and a rate-limit warning. Without an output schema, it does not list columns, but this is acceptable for a broad market snapshot tool.

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, confirmed by both the input schema and the description. With no parameters to explain, the baseline of 4 applies; the description appropriately focuses on the data returned rather than parameter details.

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 identifies the resource as '新浪财经-科创板实时行情数据' (Sina Finance STAR Market real-time quotes) and the :return: line confirms it returns a pandas DataFrame of that data. It distinguishes from siblings by specifying the Sina Finance source and KCB spot scope, though it lacks an explicit verb like 'fetches'.

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 implies usage for obtaining STAR Market real-time quotes from Sina Finance, and the warning '大量抓取容易封IP' suggests cautious use. However, it does not explicitly state when to use this tool over alternatives like stock_kc_a_spot_em (which provides similar data from Eastmoney), nor any exclusion criteria.

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