image_load

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

The description adds useful behavioral context beyond the annotations: in-band bytes are base64-encoded, `from_file` streams directly to the daemon, `~` is expanded, and file access is under the server user's permissions. It does not explicitly describe the local image-store mutation semantics, but annotations already mark readOnlyHint=false and destructiveHint=false, and loading implies writing to the daemon's image store.

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 thorough yet every sentence earns its place. It starts with the core purpose, follows with clear usage guidance and alternatives, then covers parameter mechanics and return shape in a readable format. No filler or tautology is present.

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?

Despite having no output schema, the description specifies the return type as a list of full inspect payloads per loaded image. It also covers the main usage distinctions, parameter options, file path semantics, and transfer trade-offs, making it complete enough for reliable tool selection and invocation.

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 input schema provides no parameter descriptions, but the tool description fully compensates by explaining `data` as tarball contents in-band, `from_file` as a server-host path from a `docker save`/`image_save` bundle, and the mutual exclusivity constraint. It also adds practical context about streaming and base64 encoding that is absent from the schema.

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 opens with a specific verb and resource: 'Load an image from a tarball produced by `image_save`'. It also clearly distinguishes itself from `image_pull` and `image_import`, which are the closest sibling alternatives.

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 explicitly states when to use this tool versus alternatives: registry images should use `image_pull`, flat rootfs archives should use `image_import`. It also recommends `from_file` for anything but small images and clarifies the 'exactly one of' constraint, giving an agent actionable selection criteria.

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