List checklists on a card

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

Annotations already indicate readOnlyHint=true and destructiveHint=false, so the safety profile is clear. The description adds that it includes tasks and hints at summarizing outstanding items. No contradiction.

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 two sentences plus structured Args and Example. It is front-loaded with purpose, and every part is informative without redundancy.

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?

No output schema exists, and the description does not detail the return format (e.g., list of checklist objects, fields returned). It mentions 'including their tasks' but lacks specifics. Given the simple nature of the tool, it is adequate but could be more complete.

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 has 50% description coverage – only response_format is described. The tool description explains id as 'card ObjectId', adding meaning that the schema lacks. For response_format, the schema description is more detailed, so the description adds minimal value there.

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 title 'List checklists on a card' and description 'List all checklists on a card, including their tasks' clearly state the verb (list) and resource (checklists on a card). It distinguishes from sibling tools like create_checklist, update_checklist, and list_card_comments.

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 does not explicitly state when to use this tool versus alternatives, such as when to use kanbanzone_create_checklist or kanbanzone_list_card_comments. The example provides a use case but no exclusion criteria.

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