exec_container

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

With no annotations, the description must fully disclose behavioral traits. It only states the prerequisite that the container is running, but does not mention stdout/stderr behavior, exit code handling, required permissions, or that it is equivalent to 'docker exec'. The description lacks side-effect or limitation information.

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 a single, front-loaded sentence that clearly states the tool's purpose without any filler. Every word contributes meaning, making it highly concise and well-structured.

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 simple tool with no output schema and no annotations, the description provides the core action and the running-container prerequisite, which is minimally adequate. However, it does not clarify how this differs from run_container or what happens if the container is not running, leaving some gaps for an agent selecting among many sibling tools.

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 50%: 'command' has a vague description ('Command to run'), while 'container' has none. The tool description adds no extra meaning, such as whether container accepts names/IDs or whether command can include arguments. It does not compensate for the undocumented 'container' parameter.

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 'Execute a command inside a running container' clearly identifies the action (execute), the resource (container), and the prerequisite condition (running). This distinguishes it from sibling tools like run_container, which creates a new container, or start_container, which changes container state.

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 explicit guidance is given about when to use this tool versus alternatives such as run_container or docker_compose_exec. The description implies it is for an already-running container, but it does not say 'use this when you need to run a one-off command in an existing container' or provide exclusion criteria.

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