Code MCP Server

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

No annotations are provided, so the description carries full burden for behavioral disclosure. 'Manage' is vague and doesn't specify whether operations are read-only, destructive, or have side effects. It fails to describe authentication needs, rate limits, error conditions, or what happens during operations like 'remove' or 'prune'. This leaves critical behavioral traits undocumented.

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 extremely concise at two words, with zero wasted text. It is front-loaded and efficiently states the tool's domain, though this brevity comes at the cost of clarity and completeness. Every word earns its place by establishing the scope.

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 (5 parameters, multiple actions including destructive ones like 'remove' and 'prune'), lack of annotations, and no output schema, the description is inadequate. It doesn't explain return values, error handling, or behavioral nuances, leaving significant gaps for the agent to navigate a multi-action tool safely and effectively.

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%, with all parameters documented in the schema itself (e.g., 'action' with enum values, 'volume' as name). The description adds no additional meaning about parameters beyond what the schema provides, such as explaining how 'force' applies to specific actions or what 'filter' syntax to use. Baseline is 3 since the 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 volumes' is a tautology that essentially restates the tool name 'docker_volumes'. While it indicates the domain (Docker volumes), it lacks a specific verb or resource scope that would clarify what management entails. It doesn't distinguish this tool from potential sibling Docker tools like docker_containers or docker_images beyond the 'volumes' focus.

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 provides no guidance on when to use this tool versus alternatives. There is no mention of prerequisites, when-not-to-use scenarios, or comparisons to sibling tools like docker_containers or docker_system. The agent must infer usage solely from the tool name and parameters.

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