Reorder SSH Tasks

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

Annotations already mark this as a non-read-only, non-idempotent write operation. The description adds useful context by stating it reorders all active tasks and requires the exact task set. However, it does not disclose failure behavior, stale-task handling, or workspaceId requirements.

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?

Exactly two sentences with no filler; the core operation and the critical constraint are both present and front-loaded. Every word 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 description captures the main invariant and scope well, and an output schema is present, so the return value need not be described. Minor gaps remain around workspaceId semantics and edge cases like stale taskIds, but overall the tool is adequately specified for selection and 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?

With 0% schema description coverage, the description supplies the essential meaning for taskIds: it must be the exact active task set and its order determines the new order. However, workspaceId is left undefined in both the schema and description, so the description only partially compensates for the coverage gap.

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 it reorders active SSH tasks in a workspace, with a precise scope and the key constraint that taskIds must be the exact active set. This distinguishes it from sibling task tools like delete_task, run_task, and save_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 implies the agent must obtain the current active task set before calling, but it does not explicitly say when to prefer this tool over other task operations or when not to use it. Usage guidance is mostly implicit through the 'exact active task set' constraint.

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