docker_exec

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

With no annotations provided, the description must carry the full burden of behavioral disclosure. It correctly implies a mutation (executing a command can change container state), but it doesn't specify whether the command runs interactively, whether output is returned, or what happens if the container isn't running. A score of 3 is appropriate as the description is minimally adequate but lacks depth.

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 efficient sentence with no wasted words. It's front-loaded with the core action. However, it could be more structured by adding a second sentence for usage guidelines or return information, but it earns a 4 for being concise without being under-specified.

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 lack of annotations and no output schema, the description is incomplete. A mutation tool like docker_exec should clarify output behavior (e.g., returns stdout/stderr), error handling (e.g., container not running), and lifecycle implications. The 2 parameters are well-covered by the schema, but the description doesn't help the agent understand execution semantics.

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 schema already documents both parameters. The description adds no extra semantics beyond paraphrasing the tool's purpose. For example, it doesn't explain that 'container' can be either name or ID (schema says both), nor does it clarify if 'command' should include arguments or be a single executable path. Baseline 3 is correct.

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 specifies the verb ('execute') and resource ('command inside a running container'). It distinguishes the tool from siblings like docker_start, docker_stop, and docker_logs, which manage container lifecycle or output, not command execution.

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 provides no guidance on when to use this tool versus alternatives. For example, it doesn't mention that the container must be running first (distinguishing from docker_start), nor does it explain when to use docker_exec vs docker_logs for interacting with a container. The context signals show many Docker-related siblings, making this gap more significant.

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