image_pull

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

Annotations indicate readOnlyHint=false and destructiveHint=false, so the mutation is already known. The description adds valuable context about credential requirements for private repos and the return format (dict or list), going beyond the annotations. It does not go into side effects like overwriting existing images, but for this tool the provided context is adequate.

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 and well-structured: a clear opening statement, a credential note, alternatives, parameter list, and returns. Every sentence adds value with no redundancy or filler.

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 four parameters and an output schema, the description covers purpose, usage conditions, alternatives, parameter semantics, and return values. It provides all necessary operational context without requiring additional information.

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 schema has 0% description coverage, so the description fully compensates by explaining each parameter (repository, tag, all_tags, platform) and the interaction between tag and all_tags (tag is ignored when all_tags=True). The returns section also clarifies the output shape.

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 verb 'Pull' and the resource 'an image from a registry to the daemon's local store', which is specific and distinguishes it from sibling tools like image_load (tarballs) and registry_manifest (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?

The description explicitly notes that private repositories need credentials via system_login or docker login, and explicitly recommends image_load for tarballs and registry_manifest/image_registry_data for remote inspection, providing clear when-to-use and alternatives.

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