Creates a new category in the task manager database. Provide a name and optional description to add a category for organizing tasks.
创建新分类
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | 分类名称（必填） | |
| description | No | 分类描述 |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of behavioral disclosure. '创建新分类' implies a mutation but does not mention side effects, reversibility, permissions, or failure behavior. This is a minimal disclosure for a write operation.
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 short phrase, which is concise and front-loaded. However, it is under-specified, providing no structure or elaboration beyond the bare action, so it does not fully earn its place as a useful guide.
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 mutation tool with no annotations and no output schema, the description is incomplete. It lacks information about expected behavior, error conditions, or any operational context that would help an agent decide when to invoke it correctly.
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 input schema has 100% description coverage for both parameters (name and description), so the description does not need to add parameter details. It adds no additional meaning beyond the schema, hence baseline 3 is appropriate.
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 '创建新分类' (Create new category) clearly states the action (create) and resource (category). It is not a tautology and is distinct from sibling tools like category_delete and category_list by nature, though it does not explicitly name alternatives.
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 other CRUD tools like category_update or category_list. There is no mention of context, prerequisites, or exclusion conditions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.