Create Column

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

With no annotations provided, the description carries the full burden of behavioral disclosure. 'Add' implies mutation, but the description does not state effects on existing columns, default behavior for optional fields like wipLimit or orderIndex, permissions, or whether the operation is idempotent.

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 sentence with no wasted words, which is concise, but it is also under-specified. It front-loads the core action but lacks supporting detail that would make it genuinely useful.

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 tool has 4 parameters with 0% schema description coverage and no annotations. The description is too minimal to support correct invocation: it does not explain required parameters, optional parameters, prerequisites, or expected behavior, and it leaves the agent to guess at the semantics of the input 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 0% and the description adds no meaning to the parameters. It does not explain projectKey, name, wipLimit, or orderIndex beyond their names and schema constraints, so an agent cannot infer which values are valid or how they interact.

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 uses a specific verb ('Add') and resource ('a new column') and clearly indicates the target ('to a project'). This distinguishes it from sibling tools like kanban_rename_column and kanban_delete_column, though it could be more explicit about the kanban board context.

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?

There is no guidance on when to use this tool versus alternatives such as kanban_rename_column or kanban_create_project. The description implies creation but provides no context for choosing it over other column-related tools.

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