Dokploy MCP Server

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

The description provides no behavioral information beyond what's in the annotations. Annotations indicate this is a non-readonly, non-destructive, non-idempotent operation with open-world semantics, but the description doesn't add any context about what 'createResend' actually does behaviorally - whether it sends notifications immediately, queues them, what happens on failure, or what the expected response looks like. For a tool with 11 required parameters and no output schema, this is a significant gap.

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 technically concise - just a header and parameter list - but this conciseness comes at the cost of being severely under-specified. While there's no wasted text, the structure provides no meaningful explanation of the tool's purpose or usage. The parameter list is presented but without any explanatory context, making it minimally useful despite being brief.

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 complexity (11 required parameters, no output schema, 0% schema description coverage) and the rich ecosystem of sibling tools, this description is completely inadequate. It doesn't explain what the tool does, when to use it, what the parameters mean, what behavior to expect, or what the output might be. For a notification tool with multiple configuration options among many alternatives, this description fails to provide the minimal context needed for an AI agent to use it 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?

The description simply lists parameter names and types without explaining what they mean or how they relate to each other. With 0% schema description coverage and 11 required parameters (including 7 boolean flags for different event types, plus name, apiKey, fromAddress, and toAddresses), the description fails to explain what these parameters control. It doesn't clarify what 'appBuildError', 'databaseBackup', etc. represent, or how the boolean flags interact with the notification creation/resending behavior.

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 is essentially a tautology that restates the tool name 'notification.createResend' with 'POST' added. It provides no meaningful explanation of what the tool actually does - whether it creates a notification, resends an existing one, or configures notification settings. The description fails to distinguish this tool from its many sibling notification tools like createEmail, createSlack, 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. With 11 sibling notification tools (createEmail, createSlack, createDiscord, etc.), there's no indication of what makes this 'Resend' tool different or when it should be chosen over other notification channels. No context about prerequisites, dependencies, or appropriate use cases is provided.

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