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

Annotations already declare destructiveHint=true and openWorldHint=true, so the risk profile is covered structurally. The description adds that the status is identified by name rather than ID and that positioning is optional, but says nothing about side effects such as notifications, workflow revalidation, or failure when the status name is unknown.

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?

A single compact sentence with the core action front-loaded and the optional behavior trailing in a parenthetical. Nothing is wasted or repeated.

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?

With a fully documented schema, no output schema, and annotations carrying the safety profile, the description covers the essentials. The remaining gap is behavior on invalid status names or statuses outside the current workflow, which is minor for this operation.

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 100%, so all four parameters are already documented, including the enum for placement and the referenceTaskKey pairing. The description's '(by name)' and 'positioning it relative to another task' restate schema content without adding new syntax or constraints, so the baseline 3 applies.

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 names a specific verb and resource ('Move a task to a different workflow status') plus the optional relative-positioning capability, which distinguishes it from generic siblings like update_task. It stops short of explicitly naming update_task as the alternative, so an agent must infer the boundary itself.

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?

Usage is implied by the scope of the operation, but there is no explicit when-to-use vs when-to-prefer-update_task guidance, and no mention of prerequisites such as workflow/board membership or valid status names. The '(by name)' hint and 'optionally positioning' clause give partial context.

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