docker_remove

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

With no annotations, the description must disclose all behavioral traits. It covers explicit execution timing and the on_timeout options, but omits that the tool is destructive, requires permissions, or affects volumes (force, volumes parameters).

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 brief but redundant (starts with tool name). It would benefit from separating timing details into a structured format. However, it is not overly verbose.

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?

Despite having an output schema, the description fails to convey the primary purpose and most parameter semantics. The tool has 8 parameters and 1 required; the description only adds context for the timing subset, leaving the agent underinformed.

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 0%, so the description must compensate. It explains timing parameters (expected_runtime_seconds, on_timeout, etc.) in detail, but ignores core parameters like 'container', 'force', and 'volumes', which are essential for usage.

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 restates the tool name without specifying its core function. It says 'Kali Agent MCP tool: docker_remove' but does not state that it removes a Docker container, leaving the action ambiguous.

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 docker_remove versus sibling tools like docker_stop or docker_rm. The description focuses solely on execution timing parameters, not on usage context or alternatives.

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