container_exec

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

The description discloses basic behavior: executes a command and returns output. However, it lacks detail on shell used (likely /bin/sh), handling of stderr, or non-zero exit codes. Since no annotations are provided, more transparency would be beneficial but the description is minimally adequate.

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?

Two sentences plus a brief bullet list. No extraneous content. Front-loaded with purpose statement. The structure is clean, though the Args section could be integrated more formally.

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 the simplicity of the tool (two string params, output schema exists), the description is mostly sufficient. However, it omits details like what shell executes the command, whether it returns both stdout and stderr, or exit code behavior. Minor gaps in completeness.

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 descriptions are missing (0% coverage), but the description's Args section adds clear meaning: 'Docker Container name' and 'shell command to run inside the container, e.g. "ls -la /app"'. This adds value beyond the schema and aids agent 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 clearly states it executes a shell command inside a running container and returns output. It specifies 'inside a running container', which differentiates it from sibling tools like run_container that create new containers. However, it could explicitly state that the container must already be running.

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 on when to use this tool versus alternatives like run_container, container_logs, or other sibling tools. The description implies execution of arbitrary commands but does not mention prerequisites, limitations (e.g., no interactive execution), or when not to use it.

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