docker_container_stop

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

The description labels the tool as '[DANGEROUS]' but does not explain why, nor does it disclose that stopping is irreversible, requires confirmation, or what occurs if the container is not running. With no annotations, the description fails to convey critical behavioral traits.

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?

While brief, the description is under-specified, lacking essential details that would make it efficient. It is more incomplete than concise.

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 dangerous, destructive action with no output schema, the description omits prerequisites (e.g., container must exist and be running), side effects, and confirmation behavior. It is far from 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 coverage is 0% and the description provides no explanation of the two required parameters: 'containerId' (identifies the container) and 'confirm' (a safety flag). The agent is left to infer meaning from names alone.

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 clearly states the action ('Stop') and the resource ('a running Docker container'), which directly distinguishes it from sibling tools like 'docker_container_start' or 'docker_container_restart'.

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?

No guidance on when to use this tool versus alternatives (e.g., restart or start). The description does not specify prerequisites or conditions that justify stopping a container.

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