move_task_to_list

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

The description adds no behavioral detail beyond the basic action. It does not mention side effects (e.g., removal from the old list), validation behavior, or reversibility. Annotations provide destructiveHint false, but the description itself offers negligible additional context.

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: a single-purpose sentence followed by a clear argument list. No extraneous words or repetition, making it easy to parse.

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 move operation, the description covers purpose and parameters. However, it omits potential side effects, error conditions, or prerequisites, which could matter. Given the presence of annotations and output schema, the absence of these details makes it adequate but not fully complete.

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 Args section adds meaningful semantics beyond the schema. It clarifies that task_id can be a custom ID like DEV-1234 or a UUID, and describes list_id as the target list. This helps the agent understand acceptable formats and intent, though it could be even more specific.

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 tool's purpose: 'Move a task to a different list.' This specifies the verb (move), object (task), and result (different list), distinguishing it from siblings like update_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 provides no guidance on when to use this tool versus alternatives, such as update_task if list changes are supported there. It lacks any context, prerequisites, or exclusions, leaving the agent without decision support.

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