portainer_list_unused_images

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

No annotations are provided, so the description carries the full burden. 'List' clearly signals a read-only operation, and the parenthetical ('dangling images') adds specific filtering behavior beyond the name. It does not explicitly state non-destructive intent or return format, but the verb conveys the key safety trait.

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 a single, well-structured sentence that front-loads the verb and resource. Every word adds value, and the parenthetical clarifies the exact scope without fluff.

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 simple list tool with one documented parameter, the description provides sufficient context about purpose and filtering. It does not describe return fields or pagination, but no output schema is present, and the tool's simplicity makes these omissions acceptable.

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 coverage is 100%, with environmentId fully described as 'Portainer environment ID'. The description adds no extra parameter details, so the baseline of 3 (schema already documents the parameter) is appropriate.

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 uses a specific verb ('List') and a clearly defined resource ('Docker images not used by any container (dangling images)'). This distinguishes it from sibling list_images, which likely lists all images, and directly matches the tool name.

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?

The description implies a use case (identifying unused/dangling images), but it does not explicitly state when to use this tool versus alternatives like list_images or portainer_cleanup_unused_images. No when/when-not guidance or alternative references are provided.

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