delete_checklist

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

No annotations are provided, so the description carries the full burden for behavioral disclosure. It only states 'Delete' without mentioning side effects (e.g., whether associated checkitems are also removed), permissions required, irreversibility, or response behavior. A destructive operation with no annotations needs more detail.

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 short and front-loaded, but the second sentence 'Use this tool to remove a checklist from a card' largely restates the first. It is not zero-waste; combining them would improve conciseness.

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 tool has 3 parameters, no output schema, and no annotations. The description fails to mention consequences (e.g., deleting the checklist likely deletes its checkitems), prerequisites, or return behavior. Minimal for a delete operation but still incomplete for safe usage.

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%, and each parameter (checklistId, fields, detailLevel) already has clear descriptions in the schema. The tool description adds no extra param context, so a baseline of 3 is 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?

The description specifically states 'Delete a checklist' and 'remove a checklist from a card,' clearly identifying the verb and resource. This distinguishes it from sibling tools like delete_checkitem (which deletes an individual check item) and 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?

The description explicitly says 'Use this tool to remove a checklist from a card,' giving clear context on when to apply it. However, it does not name alternatives or exclusions, so it stops short of full guidance.

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