portainer_image_remove

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

No annotations provided; description only states the action of removal. Does not disclose consequences (e.g., what happens if image is in use, irreversible changes). Lacks important behavioral context for a destructive 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?

Two efficient sentences: first clearly states purpose, second covers parameters. No unnecessary words, front-loaded with key information.

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?

While the tool is simple, the description omits output details (despite presence of output schema) and lacks safety notes. For a destructive action, more context on side effects or prerequisites would improve 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?

Despite 0% schema description coverage, the description adds meaning: it clarifies image_id format ('Image ID or name:tag') and endpoint_id behavior ('uses default if omitted'). This compensates for the schema's lack of documentation.

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 clearly states 'Remove a Docker image.' It uses a specific verb (Remove) and resource (Docker image), distinguishing it from sibling tools like inspect, pull, list.

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 this tool versus alternatives such as portainer_image_inspect or portainer_images_list. No context about prerequisites or exclusions.

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