stock_zh_b_spot

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

Annotations already cover the safety profile (readOnly, idempotent, openWorld, non-destructive). The description adds a material behavior not present in the schema or annotations: a throttling/IP-ban risk on repeated calls. This is valuable added context beyond what structured fields convey.

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?

Front-loaded with source and scope, followed by the IP-ban warning and a source URL, then the return/rtype. The URL and ':rtype:' line add mild redundancy but the text is short and each part is usable.

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 zero-parameter, no-output-schema spot tool, the description covers source, scope, the throttling caveat, and the return type (pandas.DataFrame). It is complete enough for an agent to call it correctly, with only sibling routing left implicit.

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 the baseline is 4; there is no parameter syntax the description needs to compensate for. No parameter meaning is invented or contradicted.

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?

States a specific verb+resource: real-time quotes ('实时行情数据') for all B-shares ('所有 B 股') sourced from Sina Finance. This clearly separates it from history/minutes siblings such as stock_zh_b_daily or stock_zh_b_minute, though it does not name them explicitly.

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?

Gives an explicit operational warning that repeated invocation will temporarily get the IP banned by Sina, which is genuine when-to-call guidance. It stops short of naming sibling tools as alternatives for B-share data, so it is not a full 5.

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