list_images

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

The readOnlyHint annotation already signals a safe read operation. The description adds the 'local system' scope, which is helpful context beyond the annotation, but it does not disclose any additional behavioral traits such as output format, ordering, or filtering. This meets the baseline for annotation-covered tools but adds limited extra value.

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 concise sentence that front-loads the action and resource. Every word contributes, with no redundancy or unnecessary detail.

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 tool's simplicity—no params, readOnlyHint annotation, and a clear purpose—the description is largely complete for an agent to select and invoke it. It explains what it lists and where. It doesn't detail the return format, but for a list operation this is often implied and not a critical gap.

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?

The tool has zero parameters, so the schema provides complete coverage with 100% schema description coverage. The description correctly omits parameter details as there are none. Baseline for 0 params is 4, and the description doesn't need to add anything.

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 identifies the resource 'Docker images' and scope 'local system', clearly distinguishing it from siblings like list_containers. It's unambiguous and directly states the tool's function.

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 context (local system images) but does not explicitly mention when to use this tool over alternatives like list_containers or when to prefer pull_image/remove_image. No exclusions or alternative guidance is provided, leaving usage to be inferred.

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