image_load

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

While annotations indicate it is not read-only, the description adds useful behavioral context: `from_file` is streamed to the daemon, in-band bytes are base64-encoded by MCP, and `~` is expanded. It also clarifies the return format ('One full inspect payload per loaded image') and notes that `from_file` is read by the server's user. This goes beyond the basic annotations without contradicting them.

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 detailed and well-organized with clear parameter documentation, but it is somewhat long and repeats 'exactly one of data/from_file' in both the prose and the args section. Overall, every sentence adds value, but slightly tighter phrasing could improve it.

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?

The description covers all aspects needed to use the tool effectively: what it does, parameter semantics, usage constraints, performance considerations (base64 overhead), and return value. Given no output schema, it adequately describes the return type. It is fully self-contained for an agent.

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 fully compensates by explaining both parameters: `data` as tarball contents and `from_file` as a path to a tarball produced by `docker save`/`image_save`. It also clarifies the 'exactly one' constraint and the streaming behavior, adding meaning the schema lacks.

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 tool's function: 'Load an image from a tarball produced by `image_save`' with a specific verb and resource. It also distinguishes itself from related tools by calling itself the 'counterpart of `image_save`' and contrasting with `image_pull` for registry images.

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?

It provides explicit usage guidance: 'when the image lives in a registry, `image_pull` is the normal route' and strongly recommends `from_file` for anything but small images due to base64 encoding. It also clearly states the constraint 'Pass exactly one of `data` or `from_file`', eliminating ambiguity.

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