Dokploy MCP Server

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

Annotations provide valuable information: readOnlyHint=false (mutation), destructiveHint=false (non-destructive), idempotentHint=true (safe to retry), openWorldHint=true (handles unknown inputs). The description adds minimal behavioral context beyond this - it indicates a POST operation and mentions 'reset', but doesn't clarify what gets reset, whether this affects system state, or what the expected outcome is. With annotations covering the safety profile, the description adds some value but lacks operational details.

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 - just 5 words - but this brevity comes at the cost of clarity. While it's front-loaded with the resource category, it lacks the explanatory content needed for an agent to understand the tool's purpose. The structure shows the resource and method but doesn't provide meaningful operational context. It's concise but under-specified rather than efficiently informative.

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 mutation tool (readOnlyHint=false) with no output schema, the description is inadequate. It doesn't explain what 'reset' means operationally, what gets reset, what the expected outcome is, or whether there are side effects. While annotations provide safety information, the description fails to give the agent enough context to understand when and why to use this tool versus the other whitelabeling tools. Given the complexity implied by 'reset' operations and lack of output documentation, more completeness is needed.

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?

The tool has 0 parameters with 100% schema description coverage (empty schema). The description doesn't need to explain parameters since none exist. However, it could potentially mention that no input is required, which would be helpful context. Given the zero-parameter scenario, a baseline of 4 is appropriate as the description doesn't need to compensate for any parameter documentation gaps.

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 '[whitelabeling] whitelabeling.reset (POST)' is essentially a tautology that restates the tool name and HTTP method without explaining what 'reset' means in this context. It doesn't specify what resource is being reset (whitelabeling settings? configurations?) or what the reset action entails. While it mentions the resource category ('whitelabeling'), it lacks a clear verb-object relationship that would help an agent understand the specific operation.

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 zero guidance on when to use this tool versus alternatives. There are sibling tools like 'dokploy_whitelabeling_get', 'dokploy_whitelabeling_getPublic', and 'dokploy_whitelabeling_update', but the description doesn't explain when a reset is appropriate versus getting or updating whitelabeling settings. No context, prerequisites, 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.