Move a task to another checklist

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

The description only explains parameters and gives an example, with no additional behavioral context beyond what annotations provide (readOnlyHint=false, destructiveHint=false, idempotentHint=true, openWorldHint=true). No details about side effects or return value are given.

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 concise and well-structured with a clear purpose, parameter list, and example. It is front-loaded and each part adds value.

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?

The description covers the action and all parameters, but does not mention return values or side effects. Given the tool's simplicity and the presence of annotations, it is minimally adequate but has a gap in return value disclosure.

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?

Since schema description coverage is 0%, the description compensates by describing each parameter's role. It clarifies that checklistTo can equal checklistFrom for reordering, and provides an example. However, it could explain 'position' semantics (e.g., zero-indexed) more precisely.

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 action ('Move a task') and the resource ('task'), and distinguishes between moving between checklists and reordering within the same checklist. This differentiates it from sibling tools like update_task, which modify other properties.

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 does not explicitly state when to use this tool versus alternatives like update_task. The purpose is clear enough for inference, but no direct guidance is provided.

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