get_dce_rank_table

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

Annotations already declare readOnly/idempotent/openWorld/destructive=false, so safety is covered. The description adds meaningful behavioral context beyond that: the 20200720 availability floor, the underlying-contract-only limitation, and the ~16:30 trading-day update cadence.

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?

Front-loaded with the purpose, followed by the data-availability caveat and then parameter notes. It is efficient overall, though the lengthy return-format enumeration (12 fields) makes it longer than strictly necessary for selection.

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 no output schema, the description compensates by listing the return columns (rank, vol_party_name, long/short open interest, symbol, var, date), and it documents the availability window and both parameters. An agent has enough to invoke and interpret 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?

Schema description coverage is 0%, so the description carries the parameter burden and does so reasonably: date accepts YYYY-MM-DD, YYYYMMDD, or datetime.date and defaults to today; vars_list accepts contract codes like RB/AL and defaults to all commodities. It explains both parameters clearly.

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?

States a specific verb+resource: DCE (大连商品交易所) top-20 member position ranking detail. It clearly identifies the exchange and data type, though it doesn't explicitly name the sibling rank-table tools (get_cffex_rank_table, get_shfe_rank_table, futures_dce_position_rank) it should be chosen over.

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?

Provides useful usage constraints: data only available after 20200720, the exchange only publishes underlying-contract rankings, and historical data starts 20060104 with daily updates around 16:30. However, it never states when to prefer this tool over the CZCE/SHFE/CFFEX rank-table siblings.

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