image_pull

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

Annotations declare readOnlyHint=false and destructiveHint=false. The description adds that it writes to local store (consistent with non-read-only) and lists return types. However, it omits potential side effects (e.g., overwriting existing images), dependencies (registry availability), or performance impacts.

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 a front-loaded purpose sentence, followed by a structured parameter list and return type description. Every element adds value 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?

Given the tool's 4 parameters and missing schema descriptions, the description fully documents usage and returns. Output schema information is noted (though not shown), but the description's return details suffice. No critical missing 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?

The description includes a full parameter listing with semantic explanations: repository, tag (overridden by all_tags), all_tags, and platform format. This compensates for 0% schema description coverage, adding meaning beyond the schema's raw property definitions.

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 'Pull an image from a registry to the daemon's local store,' specifying the verb 'pull,' the source 'registry,' and destination 'local store.' It distinctly separates from siblings like image_push (push to registry) and image_build (build locally).

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 explains what the tool does but provides no guidance on when to use it versus alternatives (e.g., compose_pull, image_build). It does not mention prerequisites like authentication or network access, nor conditions where it should not be used.

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