kaiten_delete_checklist

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

The annotations already disclose that this is a destructive, non-read-only operation, and the description clarifies that the target is an entire checklist within a card. It adds no detail about permanence, effects on checklist items, permissions, or error 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?

The single sentence is direct, front-loaded, and contains no unnecessary wording. Additional guidance is needed, but that gap is assessed in the other dimensions rather than as verbosity.

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-identifier deletion with destructive annotations and an output schema, the description is minimally adequate. It would be substantially more complete with ID-discovery guidance, a checklist-versus-item distinction, and a brief note on deletion consequences.

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?

The wording implies that card_id identifies the parent card and checklist_id identifies the checklist, but it never addresses the parameters directly or explains how to find valid IDs. With 0% schema description coverage, this provides only minimal compensation.

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 clearly states the verb, resource, and parent scope: deleting a checklist from a card. It does not explicitly distinguish this operation from siblings such as kaiten_delete_checklist_item or kaiten_update_checklist.

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 deletion is appropriate, when to use kaiten_delete_checklist_item instead, or how to obtain the required identifiers. The intended use is only implicit in the operation statement.

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