item.delete

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

No annotations are provided, so the description must carry the behavioral disclosure burden. It does disclose that this is a write operation and that it is protected by rate limiting and risk-control guardrails, which is useful. However, it does not state whether deletion is permanent, whether it requires authentication or special permissions, or what failure modes might result from the guardrails.

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 a single compact sentence with the core action front-loaded and the operational constraints in parentheses. It contains no filler words or redundant restatements. It is appropriately concise for a simple one-parameter operation, though more content would be needed to improve other dimensions.

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?

The tool is simple, has one required parameter, and has an output schema, so the description does not need to document return values. However, it lacks guidance on authentication, preconditions, and how the risk-control guardrails might affect invocation. For a minimal write operation, this is borderline adequate but leaves meaningful 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?

Schema description coverage is 0%, and the description does not explain the item_id parameter at all. While the parameter name is somewhat self-explanatory, the description should at least clarify where the ID comes from or what format is expected. Since the schema provides no description, the tool description needed to compensate but did not.

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 identifies the action ('下架/删除商品' — delist/delete product) and the resource, and labels it as a write operation, which distinguishes it from read-only item tools like item.get, item.view, and item.mine. It is specific enough for an agent to know what the tool does, though it does not name or contrast against a sibling such as item.publish.

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 guidance on when to use this tool versus alternatives such as item.publish or other item operations. There is no mention of prerequisites, scenarios, or when not to use it. The only context is that it is a write operation with rate/risk-control guardrails, which is a constraint rather than usage guidance.

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