docker_ps

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. It usefully discloses the default filtering behavior (running containers only unless `all` is set), and 'List' implies a non-mutating read, but it says nothing about permissions, host reachability, or result size/pagination.

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?

A single sentence with zero filler, and the default-scope nuance is placed in the parenthetical right where the reader needs it.

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 two-parameter read-only listing tool with an output schema covering return values and 100% parameter documentation, the description covers the one non-obvious behavioral nuance (default scope). Only the absence of annotation-level safety signaling keeps it from being fully complete.

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 both `all` and `server` are already documented in the schema, giving a baseline of 3. The description restates the `all` toggle semantics but adds no ordering, format, or server-identification detail 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?

Specific verb+resource: 'List containers on a Docker host' immediately tells the agent this returns Docker containers, distinguishing it implicitly from docker_images, docker_logs, docker_stats and docker_restart. It stops short of explicitly naming a sibling or contrasting scope, so it is clear but not maximally differentiated.

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 parenthetical conveys the default scope (running only) and the condition that widens it (`all`), which is genuine usage guidance. However, there is no statement of when to reach for this tool versus docker_stats, docker_logs or docker_restart, so selection guidance is implied rather than explicit.

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