load_image_from_file

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

Annotations indicate readOnlyHint=false and destructiveHint=false, which align with a non-destructive write operation. The description adds important behavioral context: streaming to daemon, handling arbitrarily large files, and path expansion for '~'. It does not mention idempotency or overwriting behavior, but the provided info is valuable.

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 four concise sentences, each adding necessary information: purpose, streaming benefit, path details, and args/returns summary. No unnecessary words.

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 simple input (one parameter) and no output schema, the description adequately covers purpose, usage, parameter semantics, and return type. It is complete enough for an agent to correctly invoke the tool.

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 compensates by explaining that file_path is 'Path to a tarball produced by docker save / save_image_to_file'. This adds critical meaning beyond the schema's bare 'string' type.

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 tar archive' with a specific verb and resource. It distinguishes itself from the sibling 'load_image' by noting that this tool handles arbitrarily large images via file streaming, unlike the in-band load_image.

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 (for large images impractical for load_image) and mentions that the file must be a tarball from docker save. It does not explicitly list when not to use it, but the alternative is implied.

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