mcp_kanban_card_manager

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

No annotations exist, so the description carries the full burden, yet it mostly repeats schema-level facts such as position ordering and checklist tasks. It discloses that cards can be deleted and moved, but not whether deletion is destructive, what fields are required per action, or what happens on partial failures.

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 compact: two sentences that front-load the resource and operation set, then add useful ordering semantics. The position explanation is dense but relevant; no filler or repetition is present.

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?

With 13 parameters, 9 possible actions, no output schema, and no annotations, this high-level overview is not complete enough. It never explains which parameters are needed for each action, how actions like move/duplicate differ, or what a successful call returns, leaving important invocation details undocumented.

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 baseline is 3. The description adds the action-oriented framing and task-list mention, but the parameter details (position, tasks, dueDate, etc.) are already fully documented in the schema, so it does not materially compensate beyond that baseline.

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 clearly identifies the resource: kanban cards inside board columns/lists, and names the main operations (creating, updating, moving, duplicating, deleting, reordering). It is distinct from sibling list/task/comment managers, though it relies on the resource term 'card' rather than naming alternatives.

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 implies use for card-level operations such as create/move/duplicate/delete, and mentions the checklist association. It provides no explicit when-to-use guidance or explicit exclusions relative to sibling tools like task_manager or list_manager, so an agent must infer the boundary.

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