list_containers

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

No annotations are provided, so the description carries the full behavioral burden. Beyond the word 'List' implying a read, it says nothing about scope (all vs. running containers), filtering, pagination, or return shape for a list operation in a very crowded tool family.

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?

Three words, front-loaded with the verb, with zero filler. It is appropriately terse for a simple list operation, though the extreme brevity leaves no room for the disambiguation the sibling set demands.

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 0-param, annotation-free tool with no output schema, the definition needs to at least distinguish itself from list_containers_simple and list_containers_by_image. As written, an agent cannot tell which container-listing tool to pick, and nothing describes what comes back.

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 tool takes zero parameters, so there is no parameter semantics to convey. The baseline for a 0-parameter tool is 4, and the description does not misrepresent the input contract.

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?

States a specific verb and resource ('List Docker containers'), so an agent immediately knows the operation. However, it offers no differentiation from sibling tools like list_containers_simple or list_containers_by_image, which an agent must resolve on its own.

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?

There is no guidance on when to use this tool versus the many near-identical siblings (list_containers_simple, list_containers_by_image, get_container, inspect_container). No prerequisites, exclusions, or alternatives are mentioned.

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