cleanup_docker

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

With no annotations, the description carries the full burden of disclosing behavior. It does clearly indicate that unused Docker images will be removed, but it leaves 'unused' undefined and does not explicitly warn that the cleanup is destructive/irreversible. This is a moderate transparency gap for a cleanup 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?

The description is five words long, immediately front-loads the action and target resource, and contains no filler. It earns its place without being bloated.

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 tool has no parameters, no output schema, and no annotations, so this sentence is the main source of context. It conveys the core action but omits safety/irreversibility information and does not route the agent away from the potentially overlapping system_prune sibling. Adequate for invocation, but not fully complete for a destructive operation.

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 tool has zero parameters, so the 0-param baseline applies and there is no parameter meaning for the description to clarify. The phrase 'Docker images' helps orient the agent to the target resource, but no parameter-level detail is needed.

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 states a specific verb ('clean up') and resource ('unused Docker images'), making the tool's basic function clear. It does not explicitly distinguish itself from the sibling system_prune, which could plausibly overlap in scope, so it falls just short of a perfect 5.

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 such as system_prune, nor any statement of prerequisites, exclusions, or safety considerations. The intended usage is only implied by the verb phrase.

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