futures_delivery_shfe

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description additionally reveals the source URL and navigation path, which is useful context. However, it does not disclose potential failure modes, data formatting, or rate limits, but the bar is lowered due to 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 relatively short and includes key elements: source URL, navigation note, parameter, and return type. The navigation steps are somewhat unnecessary for API usage but do not bloat the text. It is appropriately sized, though the '年月日' inconsistency should be fixed.

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?

This is a simple one-parameter read-only tool, and no output schema exists. The description provides a source URL and return type but does not describe the DataFrame columns or content beyond '交割情况表'. It also leaves ambiguity about the exact date format, which is critical for correct invocation. Given the low complexity, the description is moderately complete but has clear gaps.

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 provides no description for the 'date' parameter (coverage 0%), so the description must compensate. It says ':param date: 年月日' (year month day), but the default value is '202312' which is year-month format, not year-month-day. This is inconsistent and potentially misleading, though it does indicate the date parameter exists and has a default.

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 returning the Shanghai Futures Exchange delivery situation table, which is a clear resource. Although it lacks an explicit verb like 'fetch' or 'download', the return statement makes the purpose evident. It is distinguishable from sibling delivery tools for other exchanges (e.g., futures_delivery_czce) by the SHFE name.

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 navigation context (date -> monthly statistics -> dropdown) and notes that the parameter is a date, implying monthly usage. However, it does not explicitly state when to use this tool over siblings like futures_delivery_czce or futures_settle_shfe, nor does it give exclusions. The usage guidance is implied rather than explicit.

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