docker_exec

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

No annotations are provided, so the description carries the full burden for behavioral transparency. The description only states the basic operation and does not disclose potential side effects, output format, error behaviors (e.g., what if container not running), or whether a TTY is allocated. This is a significant gap for an execution tool.

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 sentence, concise and front-loaded with the action. It contains no redundant information and is easily scannable.

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?

The tool is simple and the output schema exists, so return values need not be explained. The description adequately conveys the core purpose, and the presence of sibling tools provides enough contextual distinction. Minor gaps like specifying that the container must be running are implicitly covered by the phrase 'running container'.

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?

The input schema provides descriptions for both parameters (container and command) with 100% coverage. The description adds no additional parameter semantics beyond the schema, which is the baseline expectation when schema coverage is high.

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 states a specific verb (execute), a resource (command), and the scope (inside a running container). It distinguishes from sibling tools like docker_run (which creates a new container) and docker_logs (which retrieves logs), so it scores high on purpose clarity.

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 description implies usage by specifying 'running container', which suggests using this tool when a container is already running and a command needs to be executed. However, it does not explicitly state when to use this over docker_run or other alternatives, nor does it mention any exclusions or prerequisites.

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