weeek_move_task

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. The description states the mutating behavior (move), which is clear, but it doesn't disclose whether the move is reversible, what happens to the task's position in the column, whether board_id is applied before column_id as a dependency (the schema does hint this), or what the response looks like. For a mutation tool with zero annotations, more disclosure is needed.

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 efficient sentence that states the core purpose and the key usage constraint. It's appropriately sized, though it could benefit from a brief note on parameter relationships without bloating.

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?

With 3 parameters, schema coverage at 33%, no output schema, and no annotations, this is a moderately complex mutation tool. The description covers purpose and the key constraint (at least one of two params), but lacks behavioral details like ordering semantics, reversibility, or return behavior. It's adequate but leaves gaps for a tool with this complexity.

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?

Only 1 of 3 parameters (board_id) has schema description coverage (33%), so the description must compensate for board_column_id and task_id. The description implies the board_column_id is the destination column and mentions the relationship between the two parameters, but it doesn't explain what numeric values are valid or how task_id relates. The description adds minimal value beyond the schema.

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+resource: 'Move a task to a board column (status) and/or to another board.' This distinguishes it from siblings like update_task (general updates), complete_task, and delete_task. It's specific about moving, though it could be slightly clearer on what 'status' means in the weeek context.

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 gives a partial usage constraint: 'Give at least one of board_column_id, board_id.' This clarifies when to use it logically. However, it doesn't explicitly distinguish when to use this tool vs update_task or add_task_to_project, nor does it mention any exclusions or prerequisites.

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