docker_run_container

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

The description does not disclose behavioral traits beyond the basic fact of running a container. There are no annotations, so the burden is on the description to cover behaviors like image pulling, port binding, environment variable injection, or container lifecycle (e.g., detach mode). It fails to provide this context.

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 very concise with a single sentence that front-loads the purpose. However, it is too minimal; it could include more structure or details (e.g., brief examples) without becoming verbose.

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, some optional, and no output schema, the description lacks completeness. It does not explain return values, container behavior (e.g., detached vs. foreground), or how to interact with the running container. For a tool that creates resources, more behavioral context is needed.

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%, so the baseline is 3. The description adds no additional meaning beyond the schema; it simply says 'Run a new Docker container.' While the schema already documents each parameter, the description does not compensate for any missing conceptual understanding.

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 'Run a new Docker container' clearly states the action (run) and resource (Docker container). It is specific and directly conveys the tool's function, but does not differentiate from sibling tools like docker_list_containers or docker_stop_container, which are distinct operations.

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. Sibling tools include other Docker operations and Kubernetes tools, but the description offers no context for choosing docker_run_container over them, such as when to use Docker vs. K8s or when a container needs to be run vs. stopped.

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