Delete a checklist

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

With no annotations, the description carries the burden and does disclose the two facts an agent most needs: deletion cascades to all items, and the action is reversible via app-level undo. It is silent on permissions, whether undo is time-limited or programmatic, and what the response contains, keeping it out of the top band.

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 short sentences with no waste; the destructive scope is front-loaded and the reversibility note follows immediately. 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?

The behavioral picture (cascade delete, undo available) is adequately covered for a mutation tool with no annotations and no output schema. The parameter gap is what keeps it at minimum-viable: nothing tells the agent what 'id' refers to.

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?

There is one required parameter 'id' with 0% schema description coverage, and the description never mentions it, its format, or where to obtain it. With no help in either the schema or the prose, the agent is left to guess that it is the checklist identifier.

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 ('Delete a whole checklist') and scopes it ('with all of its items'), which implicitly separates it from the sibling kanbini_delete_checklist_item that removes a single item. It doesn't name that sibling explicitly, so it falls just short of full differentiation.

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?

Usage is only implied: the agent must infer that this is the right tool when the entire checklist should go rather than one item. There is no explicit 'use this instead of kanbini_delete_checklist_item when…' guidance or prerequisite statement.

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