Code MCP Server

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It lists actions (list, pull, push, remove, etc.) but doesn't explain critical behaviors like permissions needed, side effects (e.g., 'remove' deletes images, 'prune' cleans up unused ones), rate limits, or error handling. For a multi-action tool with potential destructive operations, this is a significant gap in transparency.

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 a single, efficient sentence that front-loads the main purpose ('Manage Docker images') and provides examples. However, it could be more structured by clarifying the tool's scope or differentiating it from siblings, but it avoids unnecessary 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?

Given the tool's complexity (6 parameters, multiple actions including destructive ones like 'remove'), lack of annotations, and no output schema, the description is incomplete. It doesn't address behavioral aspects, usage context, or output expectations, leaving significant gaps for an AI agent to understand how to invoke it correctly in various scenarios.

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 description coverage is 100%, so the schema already documents all parameters (action, image, tag, force, all, filter) with descriptions and an enum for action. The description adds no additional parameter semantics beyond implying a range of actions, which the schema's enum already covers. This meets the baseline of 3 when schema does the heavy lifting.

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 'Manage Docker images (list, pull, push, remove, etc.)' states the general purpose (manage Docker images) and lists example actions, but it's vague about the specific scope and doesn't distinguish it from sibling tools like docker_containers or docker_system. It provides a high-level overview rather than a precise verb+resource definition.

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 is provided on when to use this tool versus alternatives. The description doesn't mention sibling Docker tools (e.g., docker_containers for container management, docker_build for building images), prerequisites, or specific contexts where this tool is appropriate versus others. It leaves the agent to infer usage from the action list alone.

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