portainer_images_list

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

No annotations are present, so the description full burden. It only states the action and parameter, but fails to disclose behavioral traits like side effects (none expected), authentication needs, or rate limits. The tool is a read operation, but the description does not explicitly confirm safety.

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 concise with two sentences plus an args list, no wasted words. The purpose is front-loaded, and the parameter explanation is clear and compact.

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 the low complexity (one optional parameter) and the presence of an output schema, the description is adequate. It covers the essential purpose and parameter semantics, though it could mention scope limitations (e.g., lists images only for the specified endpoint).

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 description coverage, the description adds value by explaining the 'endpoint_id' parameter as the target endpoint ID and noting the default behavior when omitted. This compensates well for the lack of schema description.

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 the action 'List' and the resource 'Docker images' with the scope 'on an endpoint', distinguishing it from sibling tools like portainer_image_inspect, portainer_image_pull, and portainer_containers_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?

The description implies usage for listing images but does not explicitly state when to use this tool versus alternatives, such as portainer_image_inspect for details of a single image. No when-not-to-use guidance is provided.

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