Dokploy MCP Server

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

Annotations provide comprehensive behavioral hints (readOnlyHint: true, destructiveHint: false, idempotentHint: true, openWorldHint: true), which already communicate this is a safe, read-only, repeatable operation. The description adds minimal value by specifying '(GET)' which aligns with the annotations, but doesn't provide additional behavioral context like rate limits, authentication requirements, or what specific destination information is returned. No contradiction with annotations exists.

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 brief (two lines) with zero wasted words, which earns points for conciseness. However, it's under-specified rather than efficiently informative. The structure with 'Parameters:' heading is clear, but the content is insufficient. While technically concise, it fails to provide meaningful information that would help an agent understand and use the tool effectively.

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 this is a read operation (per annotations) with 1 parameter but 0% schema description coverage and no output schema, the description is inadequate. It doesn't explain what a 'destination' is in this system, what information is returned, or provide any context about the parameter. While annotations cover safety aspects, the description fails to compensate for the lack of schema documentation and output information, leaving significant gaps for an agent trying to use this tool correctly.

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 0%, meaning the schema provides no descriptions for the single parameter 'destinationId'. The description only lists the parameter name without explaining what a destinationId is, its format, where to find it, or its significance. While the description acknowledges the parameter exists, it adds almost no semantic value beyond what's already evident from the schema structure.

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 '[destination] destination.one (GET)' is tautological - it essentially repeats the tool name 'dokploy_destination_one' with minimal elaboration. While it indicates a GET operation on a 'destination' resource, it doesn't specify what action is performed (e.g., retrieve, fetch, get details) or what a 'destination' represents in this context. The description fails to distinguish this tool from sibling destination tools like 'dokploy_destination_all', 'dokploy_destination_create', etc.

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 absolutely no guidance on when to use this tool versus alternatives. There are multiple sibling destination tools (create, remove, testConnection, update, all) but the description offers no context about when this specific 'one' tool is appropriate versus the 'all' tool for listing destinations or other operations. No prerequisites, use cases, or exclusions are mentioned.

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