move_task

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

No annotations are provided, so the description must disclose side effects and behavioral traits. It merely states the action without explaining what happens to the task's old tasklist, whether the move is reversible, if permissions are required, or what the return value is. This is a significant gap for a mutation tool.

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, front-loaded sentence with no filler words. It efficiently communicates the core intent without redundancy, earning a perfect score for conciseness.

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?

While the schema fully documents the parameters, the description lacks essential context for a move operation, such as whether the task will be removed from its original list, any constraints on cross-project moves, or what is returned upon success. Given the absence of annotations and output schema, the description is incomplete for an AI agent that needs to understand the tool's effects.

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?

The input schema already provides descriptions for all three required parameters, including 'Target tasklist ID to move the task to' for tasklist_id. The tool description adds no additional semantic nuance beyond the schema, so the baseline of 3 is appropriate.

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 the specific verb 'move' with a clear resource ('task') and destination ('different tasklist'). It unambiguously distinguishes from sibling tools like update_task or create_task because none of those describe relocating a task between lists. The tool name and description align perfectly.

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 provides no explicit when-to-use guidance or comparison with alternatives, such as whether update_task could also change the tasklist or if there are prerequisites. It simply states the action, leaving the agent to infer when this tool is appropriate. There is no mention of exclusions or context.

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