docker_stop

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

With no annotations, the description discloses key behavioral traits: execution timing support, timeout handling, and the difference between continue_background (returns job_id) and synchronous modes. It adds value beyond the schema but does not mention side effects like container termination signals.

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 three sentences, no wasted words. First sentence is slightly awkward but informative. It is front-loaded with the tool name and then parameter guidance.

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 thoroughly covers execution timing behavior but does not explain the primary action (stopping a container) or expected outcomes. Given the output schema exists but is not visible, and the tool has 6 parameters, the description is adequate but misses core function details.

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%, requiring compensation. The description lists the timing parameters and explains on_timeout options, adding semantic context. However, it does not describe the 'container' parameter or define each parameter individually (e.g., expected_runtime_seconds). Partial compensation.

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 name 'docker_stop' clearly indicates it stops a Docker container. The description adds 'Kali Agent MCP tool' but does not explicitly state the core function, though it is implied. It distinguishes from siblings like docker_remove and docker_run based on the name alone.

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 focuses on parameter selection (e.g., on_timeout, timeout_seconds) but does not provide explicit guidance on when to use docker_stop versus other docker tools. Usage is implied from the tool name. No alternatives or exclusions are mentioned.

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