task_start

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

With no annotations, the description must disclose behavioral traits. It states the task is asynchronous and runs under tmux, but does not mention whether the task returns immediately, what the return value looks like, or any side effects like overwriting existing tasks.

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 a single sentence, which is too concise given the lack of parameter documentation and usage guidance. It could benefit from additional structure, such as separating purpose, parameters, and usage notes.

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 is incomplete for a tool with no annotations, no param descriptions, and several sibling tools. It fails to differentiate task_start from run_remote or explain how to monitor or manage the started task. Output schema exists but is not referenced.

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 0%, yet the tool description does not explain any of the three parameters (cmd, task_name, target). The agent must infer their meanings from the tool name and context, which is insufficient.

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 starts an asynchronous task under tmux on a remote host. It uses a specific verb and resource, distinguishing it from siblings like task_kill, task_list, and run_remote.

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 provided on when to use this tool versus alternatives like run_remote. There is no mention of prerequisites, such as tmux being installed, or when an asynchronous task is preferred over a synchronous command.

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