futures_zh_spot

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the description does not need to cover safety. It adds a performance caveat ('返回数据会变慢') when adjust='1' and explains that adjust affects the return content, which is useful behavioral context beyond the 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 includes a URL and repeats '期货的实时行情数据' in both the first line and the return line. It is compact but has redundancy and unstructured docstring formatting, making it moderately concise.

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?

No output schema exists, and the return description ('期货的实时行情数据') is vague, offering no column details beyond the adjust note. It does not provide examples or clarify the full range of market values, leaving the agent uncertain about the exact data structure.

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?

Schema coverage is 0%, so the description carries the full burden. It explains symbol as contract name combination, market='CF' for commodity futures, and adjust='1'/'0' behavior along with the performance tradeoff. This is valuable, though the symbol format remains vague.

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 '期货的实时行情数据' (futures real-time market data) and specifies the return type as pandas.DataFrame, indicating a data retrieval function. However, it does not differentiate from sibling tools like futures_zh_realtime or futures_main_sina, and uses a noun phrase rather than an explicit verb+resource construction.

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. The description only provides parameter documentation and a source URL, lacking exclusions or comparisons to the many sibling futures tools.

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