futures_to_spot_shfe

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds useful context: units for different commodities (ton, gram, kilogram, barrel) and that delivery/spot volumes are one-way calculated. It also provides a source URL. However, it does not describe return formatting, error behavior, or pagination, so it adds some but not rich behavioral context.

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 lengthy list of commodity units, which is informative but adds bulk. It is structured as a title, URL, numbered list, calculation note, and type hints. However, it lacks a clear imperative purpose statement and is cluttered with details that could be summarized or moved to the output schema.

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?

With one parameter and good annotations, the tool is relatively simple. The description provides useful unit semantics and a note about one-way calculation. However, there is no output schema and the return value is only described as '上海期货交易所期转现', which is vague. The DataFrame columns and row structure are not described, making it incomplete for interpreting the 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?

The schema has one parameter (date) with no description and coverage is 0%. The docstring's ':param date: 年月' provides a year-month format hint, which is valuable given the bare schema. The default '202312' implies YYYYMM, but the description does not explicitly state the format or give additional examples.

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 first line '上海期货交易所-期转现' clearly identifies the resource (SHFE futures-to-spot) and the exchange, which differentiates it from sibling tools like futures_to_spot_czce and futures_to_spot_dce. However, it lacks an explicit verb such as 'get' or 'retrieve', making it more of a noun phrase than a directive statement.

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 provides no explicit guidance on when to use this tool versus alternatives like futures_to_spot_czce or futures_to_spot_dce. The only differentiator is the exchange name in the title, and no prerequisites or exclusions are mentioned.

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