futures_to_spot_czce

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is covered. The description adds only a source URL and return type (pandas DataFrame), but no behavioral context such as data availability, pagination, rate limits, or error conditions. This is minimal additional value 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 is short and front-loaded, with the title and URL first, followed by parameter and return docstrings. It is efficient but slightly repetitive: the title is mentioned in the description, the annotations, and the return line. No unnecessary filler, but the redundancy prevents a perfect score.

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?

There is no output schema, yet the description does not explain what columns or statistics the returned DataFrame contains. It also does not specify whether the date parameter is required, what happens with the default value, or whether the data covers a single day or a range. For a simple tool the description is still incomplete in explaining the actual output.

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 carries the burden for parameter meaning. It provides only '年月日' (year-month-day) for the date parameter, which is vague and does not explicitly clarify the format (e.g., YYYYMMDD). The default value hints at the format but is not a substitute for explicit guidance.

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 identifies the tool as retrieving CZCE futures-to-spot statistics, with the exchange explicitly named, distinguishing it from sibling tools like futures_to_spot_dce and futures_to_spot_shfe. However, it is a noun phrase rather than a clear verb+resource statement, so it does not fully meet the highest bar.

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 gives no guidance on when to use this tool versus alternatives. It does not mention that it is specific to CZCE, how it relates to other futures statistics tools, or any exclusions or prerequisites. The only hint is the exchange name in the title, which is not sufficient.

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