move_task_position

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

Description explains resolution logic for omitted parameters (swimlane_id, project) and states return value on success. Lacks error handling details but covers main behavioral traits.

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 efficient sentences covering purpose, parameter constraints, alternative tool, and return value. No redundant information.

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 description adequately covers usage, parameter constraints, and return format. While it doesn't mention all sibling tools, the key distinction from update_task is made, and resolution logic is explained.

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 coverage is 100%, but description adds valuable context: case-insensitive column_name resolution, fallback behavior for swimlane and project, and mutual exclusivity of column_id/column_name.

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?

Description clearly states 'Move a Kanboard task to a different column, position, or swimlane' with specific verb and resource, and distinguishes from sibling 'update_task' by noting it only changes board placement, not other attributes.

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?

Explicitly states 'this is the only way to change a task's board placement', provides guidance on parameter mutual exclusivity ('Provide exactly one of column_id or column_name'), and advises using 'update_task' for other attribute changes.

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