weeek_move_task

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

With no annotations, the description carries the full burden. It usefully discloses that the column target is scoped to the given board (so cross-board column names won't resolve), but it is silent on permissions, failure behavior when the column name does not exist, and whether ordering is affected.

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, front-loaded with the core action and followed by the prerequisite lookup hint. No filler.

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?

Adequate for a simple 3-parameter move with no output schema, so return values need not be described. Still missing error/edge-case behavior for an unmatched column and any note on how it relates to the other task-mutation siblings.

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 0%, so the description must compensate, and it does: it explains that column accepts a name or id (matching the string|number union) and that board_id is board-scoped and discoverable via weeek_list_boards. The task id parameter is only implied by "a WEEEK task".

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?

States a specific verb (move), resource (task), and destination (column on a board), which is enough for an agent to distinguish it from generic mutators like weeek_update_task. It does not explicitly name the sibling it competes with, but the operation is unmistakable.

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 a real prerequisite pointer ("Find board ids with weeek_list_boards"), which is more than implied usage. However it never says when to prefer this over weeek_update_task or weeek_complete_task, both of which can also change a task's column/status.

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