futures_delivery_shfe

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered. The description adds the data provenance (the shfe.com.cn statements URL) which is modestly useful context, but says nothing about output shape or any rate/access caveats.

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 resource name is front-loaded, but the docstring repeats the title in the ':return' line and adds a redundant ':rtype: pandas.DataFrame' plus an unused URL. Roughly half the lines carry no new information for an agent.

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?

For a single-read-only-parameter fetch with no output schema, the description supplies the source and a rough date format, which is minimally adequate. It omits what the returned table contains (columns, coverage period), leaving the agent to infer the payload.

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 must carry parameter meaning. It states ':param date: 年月日' (year-month-day), giving format intent beyond the bare schema, though this slightly conflicts with the '202312' default (year-month) and does not resolve the expected input string precisely.

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 names a specific resource, '上海期货交易所-交割情况表' (SHFE delivery situation table), which an agent can distinguish from delivery siblings tied to other exchanges (czce, dce). However, it is essentially a restatement of the title with no verb describing the operation, so the purpose is inferred rather than stated.

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 only prose is '注意：日期 -> 月度统计 -> 下拉到交割情况表', which is a website navigation path, not usage guidance. There is no indication of when to call this tool versus futures_delivery_czce, futures_delivery_dce, or the other delivery tools.

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