kaiten_list_checklists

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

No annotations are provided, so the description itself must carry the behavioral disclosure burden. 'List' implies a read-only operation with no mutation, but the description does not say anything about response shape, pagination, ordering, or permissions. This is adequate for a simple list read but not rich.

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?

One short, front-loaded sentence with no filler. Every word contributes to identifying the action and the target resource.

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?

This is a low-complexity tool with one required parameter and full schema coverage. There is no output schema, but 'List all checklists' reasonably implies a list of checklists is returned. A small gap remains: it does not clarify whether checklist items are included or how the result is structured.

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 schema already fully describes the only parameter, card_id, as an integer Card ID. The description adds no additional meaning or usage detail beyond what the schema provides, so the 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 uses a specific verb and resource: 'List all checklists on a Kaiten card.' It clearly distinguishes this tool from siblings like kaiten_list_checklist_items and kaiten_create_checklist by naming exactly what is returned.

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 intended context is clear: use this tool when you need the checklists belonging to a particular card. It does not explicitly name alternatives or exclusions, such as using kaiten_list_checklist_items for the items inside a checklist, so it stops short of a 5.

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