docker_cli

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

With no annotations, the description carries the full burden and largely does so: it declares which commands execute immediately, that anything else shows a preview first (a built-in safety gate), and that background=true returns a job checked via server_job. It does not explain what confirm does in relation to that preview, nor what as_root escalates.

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?

Front-loaded purpose sentence, then examples, the read-vs-write rule, and the background hint — each sentence adds information. Slightly ragged line breaks but no filler.

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?

An output schema exists so return values needn't be explained, and the execution-safety story is well covered. However, for a catch-all tool that can do anything from listing images to running privileged containers, the missing semantics for confirm, as_root and host leave real gaps an agent could get wrong.

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 0% across five parameters, so the description must compensate. It clarifies args as the text after 'docker' with good examples and explains background=true, but leaves host, as_root and confirm undefined — three of five parameters, including a privilege-escalation flag.

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 — run arbitrary docker commands — and immediately scopes it as the fallback 'for things the other docker tools do not cover', which cleanly separates it from the many docker_* siblings like docker_ps, docker_build and docker_run.

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?

Gives an explicit exclusion rule (anything the other docker tools already cover) plus concrete examples and the background/server_job workflow. It does not name which specific sibling to prefer for common tasks, so the agent must scan the sibling list itself.

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