Reorder Column Tickets

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

With no annotations, the description carries the behavioral disclosure burden. It usefully explains the priority semantics ('First ticket in the list receives priority 0'), but it does not disclose what happens to tickets omitted from ticketIds, whether the change is persistent, or whether full reordering is required.

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?

Two short sentences with no filler. The core operation is stated first, and the key ordering detail is added second, making the description easy to scan and act on.

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 is simple, has an output schema, and the description covers the basic invocation. The main missing piece is whether ticketIds must include every ticket in the column or only those whose priority is changing, which materially affects how an agent should construct the call.

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%, so the description must compensate. It clarifies that the ticketIds array order determines the new vertical order and that the first entry gets priority 0. However, columnId is left to be inferred purely from its name, and no detail is given about whether the list must contain all tickets in the column.

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 action ('Set the vertical order') and resource ('tickets in a column'), making the core purpose clear. It distinguishes itself from related actions like moving tickets between columns, though it does not explicitly name or contrast any sibling tool.

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 usage context is implied: use this tool when you need to reorder tickets within a column. However, there is no explicit guidance about when to prefer this over related tools like kanban_move_ticket or kanban_column_top_ticket, and no exclusions or prerequisites are provided.

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