gatekeeper_pull_image

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

Annotations already signal a mutating (readOnlyHint=false), non-idempotent operation. The description adds nothing beyond that: no warning that pulling can be slow, consume significant disk, require network access, or fail on missing tags. With annotations present the bar is lower, but zero additional behavioral context is provided.

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?

A single clean sentence with no wasted words and the core action front-loaded. It earns conciseness points, though the brevity stems as much from under-specification as from deliberate economy.

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 3-parameter tool with no output schema and zero schema descriptions, this is thin. An agent gets no information about return behavior, error cases (image not found, auth failure), duration/disk impact, or the meaning of pullViaCli — all relevant for a potentially long-running, mutating Docker 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?

Schema coverage is 0%, so the description must compensate — but it names no parameters. 'image' and 'tag' are self-evident from their names, but 'pullViaCli' is genuinely ambiguous (CLI vs what alternative? Docker API? gated wrapper?), and the description does nothing to clarify it.

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: 'Pull a Docker image from a registry.' This distinguishes it from siblings like gatekeeper_delete_image and gatekeeper_check_image_status. However, 'a registry' is generic and doesn't clarify whether this targets a specific configured registry or the local Docker daemon.

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?

No guidance on when to use this tool vs alternatives such as gatekeeper_check_image_status or gatekeeper_create_container. The description doesn't mention prerequisites (e.g., registry auth, daemon availability) or the role of pullViaCli, which implies a meaningful method choice the agent must guess about.

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