Reorder task

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

Annotations already indicate readOnlyHint=false and idempotentHint=true, covering the write nature and idempotency. The description adds the 'kanban drag-and-drop equivalent' analogy, which provides some behavioral context but doesn't disclose effects on other tasks or position handling beyond annotations.

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. It front-loads the action and uses a familiar analogy, making it highly scannable and effective.

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?

For a simple reorder tool, the description is adequate but lacks clarity on cross-column moves (despite column_id being required) and doesn't mention return values or edge cases. The openWorldHint and idempotentHint are not explained, leaving some context gaps.

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 100%, so parameters are well-documented. The description doesn't add meaning beyond the schema; it merely restates the general operation. This matches the baseline for full schema coverage.

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 verb ('Move/reorder') and resource ('a task'), and adds the kanban drag-and-drop analogy for context. It distinguishes from sibling tools like reorder_board_stages and reorder_daily_plan_blocks by focusing on tasks. However, the phrase 'inside a column' slightly conflicts with the column_id parameter which could imply cross-column movement, making it not perfectly precise.

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 description implies usage for reordering tasks in a kanban board but provides no explicit when-to-use guidance or comparison with alternatives. It doesn't mention exclusions or prerequisites, so the context is only implicit.

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