docker_stop

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

With no annotations, the description carries full burden for behavioral disclosure. It only mentions 'stop and optionally remove', but does not explain side effects like process termination, resource release, or behavior for already stopped containers. No mention of permissions or error cases.

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 description is a single sentence with no wasted words. The verb 'Stop' is front-loaded. However, given the low schema coverage, it could afford to be slightly longer to add value.

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?

The description is too minimal for a tool with 3 parameters, no annotations, and no output schema. It fails to explain return values, preconditions, or error scenarios. Sibling tools are not mentioned for comparison.

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 only 33% (only 'remove' has a description). The tool description adds minimal parameter context: it hints at 'remove' but does not clarify the format for 'container' (name vs ID) or the role of 'session_id'. For low coverage, the description should compensate but does not sufficiently.

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 'Docker container', and adds the optional removal behavior. It distinguishes the tool from siblings like docker_run or docker_ps. However, it could be more explicit about the effect (e.g., container becomes stopped, state changes).

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 alternatives like docker_run or docker_exec. No context about prerequisites (e.g., container must exist) or exclusions. The description simply states what it does without usage context.

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