stop_container

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

No annotations provided, so the description carries full transparency burden. It says 'stop and clean up' but does not specify whether the container is merely stopped or removed, what resources are released, or if the action is reversible. This ambiguity leaves the agent uncertain about side effects, especially for a potentially destructive operation.

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?

Two concise sentences with essential information front-loaded. No extraneous words. However, separating parameter documentation from the main description could improve clarity; as is, it mixes function and parameter details.

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?

Explains the tool's core purpose and key parameter linkage. With an output schema present, return values are covered. Missing context includes prerequisites beyond the session name, error conditions, and details on the 'clean up' process. For a stop tool with moderate complexity, the description is adequate but not thorough.

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 documentation coverage is 0%, forcing the description to explain parameters. Only the required 'name' is described ('session name passed to start_container'), while the optional 'runtime' (default 'auto') is completely omitted. The description adds minimal value beyond the schema for the name parameter and none for runtime, which could affect container behavior.

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?

Clearly states the action: 'Stop and clean up a container session' and explicitly links it to 'started with start_container', differentiating it from other container-related tools. The sibling 'start_container' confirms the paired usage.

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?

Provides straightforward usage context: this tool is for stopping a container session that was started with 'start_container'. Requires the session name from that prior call. Does not explicitly mention when not to use it or list alternatives, but the sibling list implies complementary tools like 'container_exec' for running commands.

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