Delete a tag by its ID without affecting associated tasks. Use this to remove unused or obsolete tags while keeping task data intact.
删除指定标签（不会删除已关联的任务）
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | 标签ID |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the behavioral disclosure burden. It usefully reveals that deleting a tag does not delete associated tasks, which is a meaningful side-effect guarantee. However, it does not address irreversibility, required permissions, or what happens to task-tag relationships after deletion.
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 a parenthetical clarifier that adds important behavioral nuance without unnecessary verbosity. It is front-loaded with the core action and immediately clarifies scope.
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-parameter delete tool with full schema coverage, the description covers the essential action and the main cascade risk. It lacks explicit usage guidance and deeper behavioral disclosure, but it is largely complete given the tool's simplicity.
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 100%, and the single 'id' parameter is already described as '标签ID'. The tool description adds no further parameter detail beyond saying the tag is 'specified', so the baseline score of 3 applies.
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 ('指定标签'), and adds the important qualifier that associated tasks are not deleted. This clearly distinguishes tag_delete from sibling tools like tag_list, tag_create, and category_delete.
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 does not explain when to use tag_delete versus alternatives, nor does it mention any exclusions, prerequisites, or conditions. The parenthetical clarifier implies a safe non-cascade use case, but no explicit guidance is provided.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.