image_pull

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

The disclosure that 'tag' is ignored when all_tags=True adds behavioral context beyond annotations. However, it does not explicitly state that the operation is write-oriented (consistent with readOnlyHint=false) or mention network dependencies, authentication, or potential side effects like overwriting local tags.

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, with no wasted words. It front-loads the main action and uses a structured args/returns format. Every sentence adds value.

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 the core action, parameter meanings, and return type. Although output schema exists (not shown), the description mentions the return format. It lacks details on error handling, authentication, or overwrite behavior, but is adequate for a straightforward pull operation.

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 well by explaining each parameter: repository, tag (ignored when all_tags=True), all_tags (pull all tags), and platform (os/arch format). It also notes the return type. The description could improve by providing platform format examples.

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 action: 'Pull an image from a registry to the daemon's local store.' It specifies the verb (pull) and resource (image), and distinguishes from sibling tools like image_push, image_load, and image_build, which have different purposes.

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 provides no guidance on when to use this tool versus alternatives. It does not mention when not to use it or compare with siblings like image_load or image_build, leaving the agent to infer usage context.

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