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

Annotations already declare destructiveHint=true, openWorldHint=true, readOnlyHint=false, so the risk profile is covered structurally. The description still adds value by disclosing that execution is synchronous (it 'waits for it to finish'), that the machine is persistent, and what the response contains. It does not discuss timeouts/large output truncation, which is partly handled by the schema.

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?

Three short sentences, no filler. The core action and its return value are front-loaded, and the precondition is placed last where it reads as a caveat.

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?

For a six-parameter execution tool with no output schema, the description carries the key facts: it blocks, it returns exit code/stdout/stderr, and the machine must be live. Missing is any note on output size limits or failure modes (non-zero exit vs. transport error), which would fully round out expectations.

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%, with unusually rich per-parameter docs (cwd, env, args, sh -lc auto-wrapping, timeout bounds), so the baseline is 3. The description text adds nothing about parameters beyond what the schema already explains.

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?

States a specific verb and resource ('Run a command inside a persistent Linux machine') plus the blocking behavior and return payload. It is clearly distinguishable from file-oriented siblings, but it never names an alternative (e.g. scalix_computer_read_file or scalix_sandbox_run) to anchor the distinction.

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 precondition 'The machine must be running' is genuine usage guidance. However, there is no indication of when to prefer this over siblings like scalix_sandbox_run or scalix_fn_invoke, and no mention of authentication expectations.

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