Move Entry Across Kanban

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

The description aligns with destructiveHint and idempotentHint but omits critical behavioral details such as the role of the confirm parameter and potential side effects of moving an entry across columns. It adds only the null-to-backlog behavior, which is insufficient for a destructive tool with a confirmation flag.

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 concise sentence with no filler, front-loaded with the action. However, it is so brief that it sacrifices essential operational details, making it structurally efficient but not fully helpful.

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 and a confirm flag, yet the description is only one sentence. It fails to explain confirmation semantics, prerequisites like configured kanban columns, or what 'configured column' means, leaving significant gaps for an agent to invoke it correctly.

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?

With 0% schema description coverage, the description must explain parameters. It clarifies target_column_tag_id via 'configured column' and 'backlog with null,' but entry_id, bundle_id, and especially confirm are left completely unexplained.

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 'Move' with a clear object 'entry' and destination 'configured column' or 'backlog with null.' It clearly identifies the kanban scope, though it does not explicitly compare itself to sibling bundled_move_entry, so it misses full differentiation.

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?

No guidance is provided on when to choose this tool over alternatives or when not to use it. There is no mention of prerequisites like configured kanban columns, and the only hint (null for backlog) is parameter-specific rather than tool-selection advice.

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