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 discloses that 'column' can be provided by name or id, and that the operation is 'scoped to the given board', which adds useful context. However, it does not mention potential side effects, error behavior, or whether the task must already exist on the board, leaving gaps in transparency.

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 sentence that is front-loaded with the action, contains no filler, and conveys essential information about the column parameter and board scoping. Every word earns its place, making it highly concise and well-structured.

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 mutation tool with 3 required parameters and no output schema or annotations, the description is minimally adequate. It covers the core action and key parameter semantics, but lacks information on return values, error conditions, or prerequisites. Given the simplicity of the operation, the description is workable but not rich, warranting a mid-range score.

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. It explains that 'column' can be a string (name) or number (id) and that 'board_id' determines the board scope. However, it does not explicitly describe the 'id' parameter as the task identifier, relying on inference from the verb 'Move a WEEEK task'. This partial compensation warrants a mid-range score.

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 resource 'task' and destination 'column', and adds scoping with 'scoped to the given board'. This distinguishes it from sibling tools like update_task, complete_task, and delete_task, making the purpose 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?

The description implies usage for moving tasks between columns on a board, but it does not explicitly state when to use this tool over alternatives, nor does it mention any exclusions or prerequisites. It provides context about board scoping but lacks clear guidance on choosing this tool.

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