list_docker_containers

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

With no annotations, the description carries the full behavioral burden. It clearly signals a read-only 'List' operation and discloses the return shape: a JSON string with containers, port forwards, and mount mappings. It does not mention failure modes or daemon availability, but for a list operation this is 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?

The description is concise and well-structured with distinct Purpose, Args, and Returns sections. It leads with the action and resource, contains no filler, and every sentence contributes useful information.

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?

For a one-parameter, read-only tool with an output schema, the description is nearly complete: it explains the parameter and the return payload. It only lacks explicit context about when to prefer this over related sibling commands, but this is a minor gap.

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 schema provides only the boolean name and default, with no property description. The description fully compensates by explaining the True and False behaviors: all containers vs running only. This adds meaningful semantic context beyond the schema.

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 opens with a specific action and resource: 'List Docker containers', and enumerates the contained fields: status, image, port bindings, volumes, and health. This clearly distinguishes it from sibling tools like get_docker_container_logs or get_docker_stats.

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 tool is simple enough that usage is implied by its name, and the 'all' parameter is explained. However, there is no explicit guidance about when to choose this tool over siblings such as get_docker_stats or get_docker_container_logs.

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