Docker stop

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

The description adds a behavioral detail beyond annotations: the 10-second timeout. Annotations already declare the operation is destructive and not read-only, so the description does not need to restate that safety profile.

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 entire description is one short sentence with no redundant words. The core action is front-loaded, and the timeout is presented as a concise parenthetical detail.

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 simple one-parameter tool with an output schema and safety-related annotations, the description covers the essential operation and the timeout. It does not explain return values, but the output schema handles that, and no major contextual gap remains for normal usage.

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 has one required parameter ('container') with no description, and the description provides 0% schema coverage. The description only restates the resource concept but does not clarify whether the parameter expects a container ID, name, or other identifier, so it fails to fully compensate for the missing schema documentation.

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 uses a specific verb ('Stop') with a clear resource ('a container') and adds a timeout detail, making the tool's function immediately obvious. It also distinguishes itself from sibling tools like docker_start, docker_restart, and docker_rm by naming the exact operation.

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 description clearly conveys when to use the tool: when you want to stop a container. It does not explicitly contrast with sibling tools such as docker_restart or docker_rm, but the context is clear enough to avoid obvious misuse.

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