Execute Dokploy Workflow

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

The description discloses key behavioral traits such as code execution, workflow modes, polling/cancellation for long-running runs, and resource links. The annotation 'openWorldHint: true' is aligned, and the description adds useful context beyond annotations, though it could be more explicit about side effects.

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 well-structured with clear separation of code mode and workflow mode. While it is relatively long, the length is justified by the complexity of the tool. A minor improvement could be front-loading the core purpose more succinctly.

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 (nested objects, no output schema), the description covers modes, parameters, globals, and workflow features. It mentions resource links and search, but lacks explicit details on return values or error handling, which is a minor gap.

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 coverage is 100% with detailed parameter descriptions. The tool description goes beyond the schema by explaining the purpose of globals (dokploy, helpers), usage patterns, and workflow options like target resolution and rollout. This adds significant value.

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 clearly states the tool runs JavaScript code or a guided Dokploy workflow, distinguishing two modes (code and workflow). It provides specific details about each mode, but does not explicitly differentiate from sibling tools like list_profiles or search.

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 implies when to use each mode (code vs workflow) but lacks explicit guidance on when not to use the tool or when to prefer siblings. It mentions specific workflow capabilities but does not set clear boundaries.

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