mcp_kanban_label_manager

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

There are no annotations, so the description must carry the behavioral disclosure burden. It only states that labels can be managed and added/removed in single or multiple quantities; it does not disclose side effects of delete/update, return values, per-action parameter requirements, or error behavior.

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 concise and front-loaded, listing the operation set before adding the card-specific detail. The first sentence is partially redundant with the action enum, but overall the text is short and readable.

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 tool with nine parameters, no annotations, and no output schema, the description is too thin. It does not explain which parameters are required for each action, how labelId versus labelIds differ, or what result to expect from each operation.

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 100% description coverage for all nine parameters, including enums for action and color, so the description does not need to re-explain parameter meanings. The description adds no substantive parameter detail beyond the schema, matching the baseline for high coverage.

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 labels) and enumerates the supported operations: create, update, delete, get_all, add_to_card, and remove_from_card. This is specific enough to distinguish it from the card, list, and comment manager sibling tools, though 'manage' is a generic verb.

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 no explicit guidance about when to use this tool versus alternatives like mcp_kanban_list_labels or mcp_kanban_card_manager. The second sentence hints at card-label operations, but there are no stated selection criteria, exclusions, or complementary tools.

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