move_task

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

Annotations already indicate a non-read-only mutation (readOnlyHint=false), and the description adds behavioral scope by listing reorder, reparent, and cross-list move. But it does not disclose important behavioral details such as the role of task_list_id as the source list, the meaning of previous_task_id for ordering, or whether moving across lists requires destination_task_list_id.

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?

A single, tightly written sentence that front-loads the core operations with no filler or irrelevant detail.

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 5-parameter tool with no output schema, the description and sparse schema leave critical ambiguity: the distinction between task_list_id and destination_task_list_id, the meaning of previous_task_id, and constraints around parent changes are all unexplained. An agent would need to infer or probe API behavior, making the definition incomplete for correct invocation.

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 task_id and task_list_id have schema descriptions, so coverage is 40% and the three optional parameters are left undocumented. The description maps high-level operations to parent_task_id, previous_task_id, and destination_task_list_id, but it does not explain their precise semantics, such as previous_task_id indicating the task after which the moved task should appear.

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 names three concrete operations (reorder, change parent, move to another task list) on the specific resource 'task'. This clearly distinguishes it from sibling tools like complete_task, reopen_task, and delete_task.

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 when to use the tool: when you need to reorder, reparent, or relocate a task. However, it never explicitly contrasts this with update_task or states when not to use it, leaving the agent to infer the decision boundary.

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