docker_pull_image

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

With no annotations, the description must carry the behavioral load. It does add one genuinely useful, non-obvious fact: the call requires confirm=true, which signals a gated mutation rather than a plain read. It says nothing about registry authentication, overwrite behavior for existing tags, or failure modes, so the remaining burden is unmet.

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?

Two short sentences, front-loaded with the action and an inline example, with no filler. Every clause carries information; the brevity is the right shape, the gaps are coverage rather than verbosity.

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?

An output schema exists so return values need not be explained, but for a 3-parameter mutation with no annotations and 0% schema description coverage, the definition leaves 'host' entirely undefined and omits cautionary context (auth, existing-image handling). It is not complete enough for confident invocation.

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 coverage is 0%, so the description must compensate, and it only partially does: 'image' gets a format example and 'confirm' is flagged as effectively required. The 'host' parameter — the most ambiguous one, plausibly selecting which Docker host/server the pull targets — is not mentioned at all.

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?

States a specific verb and resource ('Download an image') with a concrete format example (ghcr.io/example/app:latest), which clearly separates it from listing siblings like docker_images or building tools like docker_build. It does not explicitly name an alternative, so it stops short of a 5.

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 only guidance is the prerequisite 'Needs confirm=true'; there is no statement of when to pull versus alternatives (docker_build, docker_tag_image, docker_run), nor what happens if the image already exists locally, nor any registry/auth precondition.

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