move_task_by_name

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

Discloses partial matching and multi-match listing, but lacks details on authorization, side effects, or behavior on no match. Adequate for basic understanding but could be more transparent.

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?

Concise one-sentence purpose, behavior note, and argument list. No redundant information. Efficient.

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?

Covers main behavior (partial match, multi-match handling) and argument roles. With output schema present, return values are not needed. Reasonably complete for a move tool.

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?

Adds meaning to task_name (partial match) and lists target parameters, but lacks details on optionality, interactions, or constraints. With 0% schema coverage, description partially compensates but not fully.

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?

Clearly states verb 'move', resource 'task', and method 'by name'. Distinguishes from siblings like move_task (presumably ID-based) and search_task_by_name (just searches).

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?

Explicitly mentions partial name matching and listing multiple matches for user choice, guiding when to use this tool. Does not explicitly exclude alternatives but context is clear.

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