Docker containers

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

The readOnlyHint annotation already discloses that this is a safe read operation. The description adds useful behavioral context by noting that running containers are shown by default and that 'all=true' expands coverage, which goes slightly beyond the annotation but does not provide deeper details such as output format or environment assumptions.

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 that front-loads the core operation and then explains the one parameter's effect. There is no filler or redundant restatement of the tool name.

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?

This is a simple listing tool with one optional boolean parameter, a readOnly annotation, and an output schema. The description covers the default and all-case behavior, leaving no missing information needed to invoke the tool correctly in its likely use contexts.

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 only provides a boolean named 'all' with a default of false, and schema description coverage is 0%. The description compensates by explaining the effective meaning: running containers by default, and all containers when 'all=true'. This gives the agent enough semantic understanding to set the parameter correctly.

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 uses a specific verb and resource ('List containers'), which makes the tool's primary function immediately clear. It also clarifies the default behavior (running only) and the way to override it, distinguishing it from the many docker_* siblings that inspect, modify, or manage containers.

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 when to use the tool: when you need to list containers, especially running ones. However, it does not explicitly state when not to use it or mention alternatives like docker_inspect or docker_logs for more detailed per-container information.

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