stock_zh_b_spot

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, establishing it as a safe read operation. The description adds valuable behavioral context beyond annotations by warning that repeated executions will cause Sina to temporarily ban the IP, and it specifies the data source and return type (pandas.DataFrame).

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 extremely concise, using a single sentence (with a semicolon) to convey the tool's purpose, the IP warning, and a reference URL. The docstring-style return type is also present. Every element earns its place with no redundant information.

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?

Despite lacking an output schema, the description states that the return is a pandas.DataFrame containing real-time data for all B-shares. It also includes a critical behavioral warning about rate limiting and a direct source link. Given the tool's simplicity (no parameters), this is complete for an agent to select and invoke it correctly.

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?

This tool has zero parameters, and the schema confirms this with 100% coverage. With no parameters to document, the description is not expected to add parameter details. The description correctly explains the return value and data scope, which is sufficient given the schema baseline.

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 tool as providing real-time quotes for all B-shares from Sina Finance ('新浪财经-所有 B 股的实时行情数据'). The verb is implicit but the resource is specific, and it distinguishes from sibling tools like stock_zh_a_spot_em or stock_zh_b_daily by focusing on B-share spot data.

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 offers no guidance on when to use this tool versus alternatives. It does include a warning about repeated execution leading to IP bans, which is a usage constraint but not a comparison to sibling tools or scenarios for selection.

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