Done Bear

Edit Checklist Item

checklist_edit

Idempotent

Update a checklist item: rename it and/or set its completion state. Only the provided fields are changed; pass completed: false to uncheck an item.

Input Schema

TableJSON Schema

Name	Required	Description
`task`	Yes	Workspace-scoped task number, encoded as a string
`title`	No	New item title
`context`	Yes	Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): "Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization."
`item_id`	Yes	Checklist item UUID or prefix (>= 4 chars)
`completed`	No	Check (true) or uncheck (false) the item
`workspace`	No	Workspace id, slug, or name

Output Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes
`ok`	Yes
`action`	Yes
`taskId`	Yes

TDQS

A4/5.0

Behavior4/5

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

Annotations already provide idempotentHint=true and destructiveHint=false. The description adds valuable behavioral context beyond annotations: it explicitly states that only provided fields are changed and that 'completed: false' unchecks an item, clarifying partial-update semantics. It aligns with the idempotency annotation and gives concrete uncheck behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two sentences with no filler. The primary action is front-loaded, and the second sentence adds only the essential partial-update and uncheck behavior. Every word earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple, non-destructive update tool with full schema coverage, idempotentHint, and an output schema, the description together with the schema is sufficient for an agent to call it correctly. The only notable gap is explicit routing relative to checklist_done, but that is more a usage-guidance issue than a completeness issue for invoking the tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3. The description reinforces parameter meaning ('rename' maps to title, 'completion state' maps to completed) but adds little beyond what the schema already documents. It does clarify that fields are optional and only provided ones are changed, which slightly aids parameter understanding.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb and resource: 'Update a checklist item' and explicitly lists what can be changed ('rename it and/or set its completion state'). This clearly separates it from checklist_add, checklist_remove, and even checklist_done by covering both renaming and unchecking functionality.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies when to use the tool: when a checklist item needs its title changed or its completion state toggled, including unchecking via 'completed: false'. However, it does not explicitly name or exclude alternatives such as checklist_done, so an agent must infer the boundary between this tool and the sibling completion tool.

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

All Done Bear tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.6/5.0

Disambiguation4/5

Tools are grouped cleanly by resource (task, checklist, comment, label, project, attachment), so most actions have an obvious owner. The main ambiguities are task_list vs. search and checklist_done vs. checklist_edit, but the descriptions call out the intended boundaries clearly enough to avoid frequent misselection.

Naming Consistency4/5

The dominant resource_verb pattern (task_add, task_edit, checklist_list, comment_remove, project_join) is consistent and predictable. A few outliers like get_context, guide, search, and task_attachment_list break the pattern, but the naming remains readable and mostly uniform.

Tool Count2/5

At 35 tools, this is a very large surface for an agent to choose from and exceeds the 25-tool threshold where count becomes a liability. The tools are well organized, but the repeated verb families across six resources make the total feel heavy even though each tool is plausibly justified.

Completeness4/5

The core task lifecycle is well covered: create, show, edit, list, complete, reopen, archive, assign, and bulk operations, plus full checklist, comment, label, and attachment workflows. Notable gaps are the lack of an explicit unarchive/restore path and no label edit/delete, but these are minor enough that agents can usually work around them.

Resources

Need Help?