mcp_kanban_batch_cards

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

With no annotations, the description carries the full burden for behavioral disclosure. It discloses behaviors beyond the schema: labels are auto-created on the board if missing, position has a default (65535) with explicit ordering semantics, and checklistName has a default of 'Checklist'. These details add contextual depth beyond raw parameter names.

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 a single compact paragraph that front-loads the core operation and then packs several key behaviors inline. It is efficient with no wasted sentences; a slight deduction for density—one long sentence carries a lot of nested conditional detail that could be structured for easier scanning.

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?

For a batch-create tool with 100% schema coverage, the schema already carries the heavy lifting for constructing a payload. The description covers the one critical behavioral context not inferable from the schema alone: label auto-creation and defaults. Return values are not explained, but the absence of an output schema makes that acceptable, so the definition is complete enough.

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 all parameters and defaults. The description still adds value by clarifying the task-in-checklist structure (task ∈ checklist ∈ card), label auto-creation semantics, and the per-card override behavior. It does not repeat every schema detail, but the added value is modest rather than essential.

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 states a specific verb ('create multiple cards at once') with a clear resource and scope. It enumerates what each card can include and is clearly distinct from siblings like mcp_kanban_card_manager which likely handles single-card operations.

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 when to use it—when creating multiple cards in one call—but does not explicitly state exclusions or alternatives, e.g., when a single-card tool would be preferred. No explicit routing to siblings despite the batch nature being clear from name and first sentence.

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