Permanently deletes a checklist item from a Trello card using card and checklist item IDs; use it to remove an item, not to mark it complete.
Permanently delete one checklist item. This cannot be undone; use card_checklist_item_set_checked to mark completion while keeping the item.
| Name | Required | Description | Default |
|---|---|---|---|
| cardId | Yes | Trello card id, short link, or Trello card URL. | |
| checkItemId | Yes | Trello checklist item id. |
Changes observed during successful MCP inspections.
v1.0.4Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full behavioral burden. It usefully discloses that deletion is permanent and cannot be undone, but it does not mention permission requirements, side effects on the parent checklist, or response behavior.
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 compact sentences with the destructive nature front-loaded and the alternative immediately following. Every sentence earns its place.
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 simple two-parameter destructive tool with no output schema, the description covers the essential risk and routing information. It could still do more on permissions or side effects, but it is largely complete.
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%, so both cardId and checkItemId are already documented. The description adds no parameter-specific syntax or constraints beyond the schema, making the baseline 3 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?
States a specific verb and resource: "Permanently delete one checklist item." It also distinguishes the operation from the sibling alternative card_checklist_item_set_checked, so an agent can tell what this tool does.
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?
Gives a clear alternative for the common non-destructive case: use card_checklist_item_set_checked to mark completion while keeping the item. It does not spell out broader when-not-to-use conditions, but the destructive intent is clear.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.