ssh_run_background

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

Describes detached execution via nohup, but doesn't detail side effects, error handling, or whether output persists across sessions. Still useful given no annotations.

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?

Front-loaded purpose, then structured Args section. Every sentence is necessary and informative. No redundancy.

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?

Covers main usage and behavior, but lacks mention of immediate response/return value (likely job_id) and error scenarios. Still adequate for a well-understood task.

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 coverage, the Arg section fully explains each parameter: command, cwd (defaults), job_id (auto-generated), host (uses default). Adds meaning beyond schema.

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 purpose: 'Start a long-running command in the background on the remote server.' It distinguishes from sibling ssh_run (foreground) and references ssh_job_status for follow-up.

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?

Explicit guidance: 'Use this for commands that take more than 30 seconds (e.g., builds, test suites).' Also directs to use ssh_job_status for progress, implying not for short tasks.

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