mcp_kanban_list_manager

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

With no annotations, the description itself must disclose behavioral scope, and it does clarify that it operates on top-level board columns containing cards. It does not, however, describe the effects of destructive actions such as delete, permissions needed, or whether cards are affected when a column is removed.

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 tight sentences with no wasted words. The clarifying 'IMPORTANT' note is placed right after the main purpose recognized and clearly flags the most likely misuse.

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 description is adequate for tool selection and scope understanding, but it is incomplete for a manager with five actions. It does not outline what each action requires, mention that create/update/delete have different parameter obligations, or describe expected return behavior in the absence of an output schema.

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%, so the schema already documents each parameter. The description adds useful domain context about what a 'list/column' is, but it does not add action-specific parameter requirements, such as which parameters are needed for create versus update.

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 names a specific resource ('kanban board lists/columns') and provides concrete examples ('Backlog', 'To Do', 'In Progress', 'Done'). It also draws a clear boundary against card task-lists and sub-tasks, which prevents confusion with sibling card/task tools.

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 gives an explicit when-not signal: it is NOT for card task-lists or sub-tasks inside cards. However, it stops short of naming the correct sibling alternative (e.g., mcp_kanban_task_manager), leaving some inference to the agent.

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