move_task_to_list

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

No annotations are provided, so description carries the full burden. 'Move' implies mutation and possibly removal from the source list, but the description doesn't clarify whether the task is removed from its original list, whether any per-list custom field values are lost, or what the return behavior is. Adequate baseline but lacks behavioral detail.

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?

Single concise sentence that fully communicates the core operation. Zero waste, appropriately terse for a simple two-parameter tool.

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 two-parameter mutation tool with no annotations and no output schema, the description is unusually sparse. It's functional but doesn't communicate the side effect of the move (removal from source list), which is the most important behavior the agent should understand. Adequate but could provide more.

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 100% - both list_id and task_id are described in the schema. The description adds no additional parameter context beyond what the schema already provides, which is the baseline 3. No explanation of relationship between task and list.

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?

Clear verb+resource+action: 'Move a task to a different list' specifies the operation and its subject. However, it doesn't differentiate from siblings that also operate on tasks (e.g., update_task, duplicate_task), though it's distinct enough from tag/watcher/comment tools.

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?

No guidance on when to use this tool versus alternatives like update_task (which could also change list assignment) or duplicate_task. No context about cross-workspace restrictions or prerequisites.

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