Delete Checklist Item

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

Annotations already declare destructiveHint=true, but the description adds critical behavioral context: Kaiten resolves the deletion by itemId alone, so incorrect cardId/checklistId values still delete the real item. This warning goes beyond the schema and annotations and is essential for safe use.

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 three sentences with no filler: the action is front-loaded, the ID sourcing is explicit, and the critical warning is placed last for emphasis. 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 destructive single-item deletion tool, the description covers what is deleted, where the IDs come from, and the key safety caveat. No output schema exists, but deletion tools generally don't need return-value detail, and the annotations plus description together give an agent everything needed 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?

Schema description coverage is 100%, so the baseline is 3. The description adds meaningful parameter semantics by stating that all three IDs originate from kaiten_get_checklist and by clarifying that itemId is the authoritative resolver while cardId/checklistId are not validated. This is valuable beyond the schema's simple 'ID' descriptions.

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: 'Remove a single item from a checklist.' It clearly differentiates from sibling tools like kaiten_delete_checklist and kaiten_update_checklist_item by emphasizing 'single item,' so an agent can distinguish it without opening schemas.

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 clear context by instructing that cardId, checklistId, and itemId should all come from kaiten_get_checklist, and it gives a safety directive: 'Verify the pair before deleting.' It does not explicitly name when not to use the tool versus alternatives, but the usage context is strong enough for correct selection.

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