image_remove

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

The description discloses critical behaviors beyond the destructiveHint annotation: it details failure conditions, force behavior, and side-effects of noprune. No contradiction with annotations.

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 well-structured with core purpose first, then edge cases, then parameter docs. It is slightly verbose but every sentence adds value; minimal redundancy.

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?

Given an output schema exists and returns bool, the description covers all parameters, edge cases (multiple tags, stopped/running containers), side-effects, and links to image_tag. No gaps for an agent to use this tool correctly.

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?

With 0% schema coverage, the description fully defines each parameter: id_or_name includes optional tag/digest, force overrides specific blocks, noprune preserves untagged parent layers. This adds significant meaning beyond the schema's type/default.

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 starts with 'Remove a local image by name or id,' clearly stating the action and resource. It distinguishes from siblings like image_tag by explaining when to untag first, and from image_prune by focusing on single image removal.

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?

Explicitly explains when force is needed (multiple tags or stopped containers), when it fails (running containers always block), and when to use image_tag first. It also advises on noprune usage, providing clear guidance on alternatives and exclusions.

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