image_load

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

Annotations are minimal (readOnlyHint false, destructiveHint false). The description adds context: the tool requires exactly one of two sources, explains streaming behavior for `from_file`, and notes that `from_file` is read by the server user with `~` expansion. It does not detail side effects like tag conflicts, but the added value is substantial.

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 at about 5 lines, front-loaded with the core purpose, then parameter details. Every sentence contributes unique information without redundancy.

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 tool with 2 parameters and no output schema, the description covers the input sources, streaming optimization, and return type (list of image attrs). Minor gaps: no mention of tag overwrite behavior or error conditions, but overall adequate for agent decision-making.

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 has no parameter descriptions (0% coverage). The description fully compensates by explaining `data` as tarball bytes in-band (base64 encoded), `from_file` as a server path streamed to daemon, and the mutual exclusivity constraint. This adds essential meaning beyond 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 clearly states 'Load an image from a tarball produced by image_save', specifying the verb 'load' and resource 'image from tarball'. It distinguishes from the sibling tool `image_save` which is the inverse operation.

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 gives explicit guidance on when to use each parameter: 'Pass exactly one of `data` (tarball bytes in band) or `from_file`... preferred for anything but small images'. It explains streaming and base64 encoding trade-offs. However, it does not compare to alternative image loading methods like `image_pull`, which is in the sibling list.

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