Yougile Move Task

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

The description discloses an important behavior beyond annotations: when a workflow chain is configured, the tool walks through intermediate columns because YouGile rejects jumps. This adds value since annotations only carry destructiveHint=false. However, it omits the confirmation-required behavior that the confirm parameter hints at, and does not describe any other side effects or failure modes.

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, front-loaded with the primary action, then a concise important nuance. No filler or redundancy. Every sentence earns its place.

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 tool has five parameters including 'board' for cross-board moves and 'confirm' for approval flows, but the description does not mention these scenarios. It also does not describe return values. The workflow-chain note is helpful, but the description leaves the confirmation flow and cross-board move behavior unexplained, which are material for correct invocation.

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?

Schema description coverage is 80%, so the schema already documents most parameters. The description adds no direct parameter explanations, but the workflow-chain context indirectly clarifies how the 'column' parameter behaves on chain-configured boards. Baseline 3 is appropriate given high schema coverage.

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 states the action clearly: 'Move a task to another column.' It identifies the resource and the target, and the workflow-chain nuance adds specificity. However, it does not explicitly differentiate from sibling tools like yougile_update_task or yougile_create_task, though the verb and resource are distinct enough.

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?

No guidance is given on when to use this tool versus alternatives. The description does not mention conditions that would favor this over yougile_update_task or when moving is not appropriate. It only adds a behavioral note about workflow chains, which is not selection guidance.

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