futures_zh_daily_sina

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered structurally. The description adds the Sina source URL and a pandas.DataFrame return rtype, which is useful operational context, but omits any note on return columns, history depth, or rate limits.

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 purpose is front-loaded, but the body is raw docstring boilerplate (:param/:type/:return/:rtype) with a bare URL pasted mid-entry. Functional yet not tightly edited.

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 single-param read-only tool with annotations already covering safety and no output schema, the description supplies the source, symbol acquisition path, and return type. The remaining gap, what columns the DataFrame contains, is minor.

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 description coverage is 0%, so the description must carry the parameter. It does add real value by explaining that symbol comes from match_main_contract(symbol="cffex") or the source web page, even though it never mentions the RB0 default present in the schema.

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 opening line states a specific resource and cadence: Chinese futures data across all varieties at daily frequency. That distinguishes it from the minute-level sibling futures_zh_minute_sina, though it never names or contrasts alternatives 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?

The only guidance is embedded in the symbol param note (call match_main_contract or scrape the page), which implies but never states the intended use case. There are no when-to-use or when-not-to-use conditions relative to the many other futures tools.

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