move_task_position

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

With no annotations, the description discloses key behaviors: case-insensitive column name resolution, default swimlane handling, project resolution, and return value. It does not detail side effects or error conditions, but is fairly transparent for a mutation tool.

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?

Three sentences with no redundant content. First sentence states purpose, second gives column specification, third covers swimlane and project resolution. Efficient and front-loaded.

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?

Given empty schema and no output schema, the description covers main functionality, parameter usage, and return value. It does not explain 'position' semantics or error handling, but is largely complete for a move 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 input schema is empty, yet the description meaningfully defines parameters (column_id, column_name, swimlane_id, project_id, project_identifier) that are not in the schema. It adds value by explaining how to use them, though types and requiredness are not specified.

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 states the tool moves a task to a different column, position, or swimlane, specifying the verb 'move' and the resource 'task position'. It distinguishes from sibling tools like move_column and move_swimlane which operate on columns/swimlanes, not tasks.

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?

Provides clear instructions: 'Provide exactly one of column_id or column_name' and explains resolution for swimlane and project. It gives context for use but does not explicitly state when not to use this tool versus alternatives like update_task.

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