delete_workitem

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

Annotations already declare destructiveHint=true, readOnlyHint=false and idempotentHint=false, so the danger profile is covered. The description adds useful scoping context (only workitems within the current project) and reinforces the confirmation gate, but says nothing about whether the delete cascades to comments/files, whether it is recoverable, or what errors occur for out-of-project ids.

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?

Two short sentences, zero filler, with the destructive action and its hard requirement front-loaded in that order. Nothing is wasted or buried.

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?

An output schema exists, so return values need no explanation, and the destructive nature is covered by annotations. Still, for an irreversible delete tool the description omits side effects on dependent objects and permission requirements, leaving an agent to guess at the blast radius.

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 param meaning; it does explain that confirm must be explicitly true, which is the non-obvious parameter. However, workitem_id's format constraint (pattern ^[A-Za-z0-9._-]{1,64}$) and whether it must belong to the current project are left entirely undocumented.

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 states a specific verb (删除) and resource (工作项) plus a scope constraint (当前项目内), which lets an agent distinguish it from list/get/update workitem siblings. It does not explicitly name delete_workitem_comment as the alternative for comments, so it stops short of full sibling differentiation.

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 guidance is the mechanical requirement to pass confirm=true, which merely restates what the required field in the schema already enforces. There is no indication of when deletion is appropriate versus update_workitem, no prerequisites (permissions/ownership), and no warning about irreversibility or impact on related data.

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