move_task

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

The description adds significant behavioral context beyond annotations: it explains the recreate-then-delete mechanism, lists preserved fields, flags unsupported items (checklistItems, linkedResources), and notes that the task ID changes. Contradicts no annotations.

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?

Two sentences plus a note, all essential information. No wasted words; front-loaded with the core action.

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 tool with no output schema, the description covers key invocation details (parameters, behavior, limitations). It omits return value format (though 'verbose' parameter hints at it), but overall is sufficient for an agent to use correctly.

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 one parameter ('verbose') is described in the schema; the three required parameters (source_list_id, task_id, target_list_id) have no descriptions. The tool description indirectly clarifies their roles but does not provide explicit semantics. Schema description coverage is low (25%), but the description partially compensates.

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 explicitly states the action ('move a task from one list to another') and lists preserved fields, distinguishing it from create/delete pairs and sibling tools like 'create_task' or '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 clearly indicates the tool is for moving tasks between lists, but does not mention when not to use it (e.g., if preserving checklist items is important) or provide explicit alternatives.

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