get_rank_table_czce

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false. The description adds meaningful behavioral context: accepted date formats, default-to-today behavior, the return type as pandas.DataFrame, and a URL pointing to the source. It does not mention rate limits or failure modes, but for a read-only retrieval tool these are less critical.

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 structured into clearly labeled sections (source URL, note, param, return, return format) and is information-dense. It is somewhat long, but every section adds necessary detail; the field table is valuable given the absence of an 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 no output schema and minimal input schema, the description provides a complete field-by-field breakdown of the returned DataFrame, explains the date parameter thoroughly, and notes the exchange-specific behavior (both variety and underlying rankings). This is fully sufficient for an agent to invoke and interpret the result.

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 input schema only defines 'date' with no further explanation (coverage 0%). The description fully compensates by specifying accepted formats (YYYY-MM-DD, YYYYMMDD, datetime.date) and the default behavior (today if empty), which is essential for correct invocation.

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 the tool retrieves Zhengzhou Commodity Exchange (CZCE) top 20 member position ranking data, with a specific resource and verb. It distinguishes from sibling rank-table tools (e.g., get_dce_rank_table, get_cffex_rank_table) via the explicit '郑州商品交易所' (CZCE) and top-20 scope.

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 context is implied: the tool is for CZCE ranking data, and the note about both variety and underlying rankings clarifies data granularity. However, it does not explicitly state when to use this tool versus alternatives like get_rank_sum or other exchange rank tables, and no exclusions or alternative tool names are mentioned.

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