image_pull

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

Annotations already indicate non-read-only, non-destructive behavior. The description adds context about pulling to the local store and requiring credentials for private repos, which goes beyond annotations. It does not mention rate limits or failure modes, but these are not critical.

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?

Well-structured with clear sections: purpose, usage guidance, args, and returns. Front-loaded with the main purpose and no redundant sentences.

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 tool's moderate complexity, the description is complete: it covers prerequisites, alternatives, parameters, and returns. An output schema exists, so return details are optional, but the description still provides useful context.

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 0% parameter description coverage, so the description compensates by listing all four parameters with explanations. It adds a useful refinement: 'tag ignored when all_tags=True' and describes the return format.

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 states a specific verb+resource: 'Pull an image from a registry to the daemon's local store.' It also distinguishes from siblings by explicitly mentioning image_load (for tarballs) and registry_manifest/image_registry_data (for remote inspection).

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?

Provides explicit guidance on when to use this tool vs alternatives: 'Use image_load for tarballs, and registry_manifest / image_registry_data to inspect a remote image without pulling it.' Also warns about credentials for private repositories as a prerequisite.

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