ssh_task_launch

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

No annotations provided, so description carries full burden. It discloses background execution, non-waiting behavior, output redirection to files (not memory), and return of PID/task info. Does not discuss side effects (e.g., sudo password prompts) but core behavioral traits are 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?

Extremely concise: two sentences plus return note. Key purpose is front-loaded. No wasted words.

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?

Given 5 parameters all well-described in schema, and an output schema exists (context confirms true), the description need not detail return structure. Sibling tools are many but this description clearly differentiates the tool. No apparent gaps.

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 coverage is 100%, but description adds value: explains output is redirected to files (default paths given), log_output defaults to true, stderr_log defaults to stdout_log. Adds context beyond schema descriptions.

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?

Description clearly states it launches a command in the background and returns PID. It distinguishes from ssh_run by noting it does not wait for completion. Verb+resource+key differentiator present.

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 contrasts with ssh_run ('Unlike ssh_run, this does not wait...'), guiding when to use this tool. Mentions output redirection to files, implying use cases where in-memory capture is not needed. No explicit when-not-to-use, but comparison with sibling is strong.

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