Add an item to a Kaiten card checklist with optional checked state, sort order, due date, and responsible user.
Add a checklist item with optional completion, order, due date and responsible user.
| Name | Required | Description | Default |
|---|---|---|---|
| text | Yes | ||
| card_id | Yes | ||
| checked | No | ||
| due_date | No | ||
| sort_order | No | ||
| checklist_id | Yes | ||
| responsible_id | No |
| Name | Required | Description | Default |
|---|---|---|---|
| item | Yes |
Changes observed during successful MCP inspections.
v1.2.0Input schema / properties / card_id / maximumRemoved value: -9007199254740991Input schema / properties / checklist_id / maximumRemoved value: -9007199254740991Input schema / properties / due_date / anyOfPrevious value: -[
- {
- "anyOf": [
- {
- "format": "date",
- "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))$",
- "type": "string"
- },
- {
- "format": "date-time",
- "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d:[0-5]\\d(?:\\.\\d+)?(?:Z|([+-](?:[01]\\d|2[0-3]):[0-5]\\d)))$",
- "type": "string"
- }
- ]
- },
- {
- "type": "null"
- }
-]New value: +[
+ {
+ "anyOf": [
+ {
+ "format": "date",
+ "type": "string"
+ },
+ {
+ "format": "date-time",
+ "type": "string"
+ }
+ ]
+ },
+ {
+ "type": "null"
+ }
+]Input schema / properties / responsible_id / maximumRemoved value: -9007199254740991v1.0.2Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description is consistent with the annotations, which establish a non-read-only, non-idempotent, open-world operation. Beyond those annotations, it adds little behavioral context such as defaults for omitted fields, ordering behavior, permissions, or other side effects.
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 single sentence is compact and front-loads the action and resource. The optional-field list adds useful information without redundancy or unnecessary wording.
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 description is minimally adequate for a straightforward creation tool, especially since annotations and an output schema are present. However, seven undocumented parameters and the absence of selection guidance or creation semantics leave noticeable 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?
With 0% schema description coverage, the description usefully clarifies that completion, order, due date, and responsible user are optional, corresponding to checked, sort_order, due_date, and responsible_id. It does not explain the identifier parameters, where to obtain them, or add meaningful guidance for text and date values.
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 action and resource: adding a checklist item, with its main optional attributes. It does not explicitly distinguish this operation from kaiten_create_checklist or from modifying an existing item with kaiten_update_checklist_item.
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?
Usage is implied for creating a new checklist item, but there is no explicit when-to-use guidance or prerequisite context. It does not direct agents to kaiten_update_checklist_item for existing items or provide any when-not conditions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.