kaiten_delete_checklist

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

Annotations already declare destructiveHint=true, idempotentHint=false, and readOnlyHint=false, so safety is covered structurally. The description adds nothing beyond the annotations: it does not say whether deleting a checklist also destroys its items, whether the deletion is reversible, or what permission is required.

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?

A single front-loaded sentence with zero filler, so nothing is wasted. Its brevity is a virtue structurally, though it comes at the cost of the missing detail noted in other dimensions.

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 mutation with two undocumented IDs, an output schema present, and a dangerous sibling (delete_checklist_item), the description should at minimum note cascade behavior and how to obtain the IDs. As written it is not sufficient for confident invocation.

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 0% for both required parameters. The phrase 'from a card' loosely implies card_id, but neither card_id nor checklist_id is explained, and no format, ID-source, or constraint detail is provided to compensate.

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 gives a clear verb (Delete) and resource (checklist) plus scope (from a card), so the action is unambiguous. However, it does nothing to separate itself from the nearby sibling kaiten_delete_checklist_item (which deletes an item, not the list), so an agent must infer the distinction from names alone.

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?

There is no guidance on when to use this versus kaiten_delete_checklist_item, kaiten_update_checklist, or kaiten_archive_card, and no prerequisites or warnings are stated. The agent gets the action but no routing context.

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