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

Goes well beyond the annotations (destructive/openWorld/idempotent=false) by disclosing return shape (exit code plus only the tail of output), truncation behavior, that over-bound command/stdin/timeout is refused with the offending parameter named, that failure to start surfaces as exit 127/126 with Docker's error in stdout, and that output is untrusted.

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?

Purpose and return contract are front-loaded in the first clause, and every later sentence carries real operational information. The telegraphic fragments ('Over a bound on command, stdin or timeout = refused (named)') cost some readability but nothing is wasted.

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 destructive, open-world exec tool with no output schema, the description covers return values, truncation, refusal and failure modes plus a security caveat. It stops short of stating permission/auth requirements or environment restrictions, which are the remaining 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 71% and the schema already documents stdin, command, run_as_user, timeout_seconds and working_directory. The description adds the useful refusal semantics tied to the command/stdin/timeout bounds, but service and project_id remain undocumented and no syntax detail is added beyond the schema's examples.

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 ('Runs a command in a running service's container') and anchors it to a familiar analogue ('like `docker exec`'), which immediately separates it from siblings such as RunMachineAction, RunProjectAction and QueryContainerLogs.

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?

Usage is implied by the docker-exec analogy, and refusal conditions are given, but the description never states when to choose this over the sibling action/log tools or any prerequisites for calling it.

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