Docker exec

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

Annotations already flag this as destructive, so the description does not need to restate that. It adds value by disclosing that --privileged is blocked, a meaningful security boundary. The core behavior of running a shell command inside a container is clearly stated.

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 extremely concise and front-loaded. Every word earns its place: the primary action, the target resource, and the key security restriction are all included with no filler.

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 relatively simple and has an output schema plus annotations covering destructiveness, so the description does not need to explain return values. However, it leaves important operational context unstated, such as whether the container must already be running and how timeout_seconds affects execution.

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 0%, so the description carries the burden of explaining parameters. It loosely maps 'command' via 'Run sh -c' and 'container' via 'inside a container', but it completely omits timeout_seconds and gives no detail on command format or container identifier expectations.

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 states a specific action ('Run sh -c') and a specific resource ('inside a container'), which clearly identifies the tool's function. It is inherently distinguishable from sibling tools like docker_ps, docker_logs, or docker_inspect, none of which execute arbitrary commands inside a container.

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 gives no explicit guidance on when to use this tool versus alternatives such as run_command, docker_logs, or docker_start. The only qualification is '--privileged blocked,' which is a constraint rather than a usage guideline.

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