image_rm_tool

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

With no annotations provided, the description carries the full burden of behavioral disclosure. 'Remove an image' implies deletion but fails to mention that removal may fail if the image is in use, how the 'force' parameter affects behavior, or that removal is irreversible. This is a significant gap for a mutation tool.

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 very brief and front-loaded, but it is under-specified rather than elegantly concise. It provides no additional context beyond the tool name, so it does not add value beyond a simple label.

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?

For a tool with 2 parameters, an output schema, and many siblings, the description is incomplete. It fails to explain when to use this tool, what happens on force removal, or what the return value indicates. The lack of annotations further reduces contextual completeness.

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 100% for both parameters (name and force), so the schema already explains their meaning. The description adds no parameter-specific information, which is acceptable given the schema coverage, warranting the baseline score of 3.

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 'Remove an image' clearly states a specific action (remove) and resource (image). However, it does not explicitly differentiate from sibling tools like image_prune_tool, which also deals with removing images, so it lacks sibling distinction.

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 is given on when to use this tool versus alternatives such as image_prune_tool or container_rm_tool. There is no mention of prerequisites, exclusions, or typical use cases, leaving the agent without decision support.

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