dokploy_infrastructure

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

No annotations provided, and the description does not disclose behavioral traits such as persistence, side effects, idempotency, or permission requirements. For mutating operations, 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?

Extremely concise: one sentence summarizing purpose and listing actions with required params. No fluff, front-loaded with 'Manage ports, auth, certs.'

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 complex tool with 16 parameters and multiple sub-actions, the description lacks detail on outputs, error handling, and optional parameters. Users would need external documentation.

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?

Description maps required parameters to each action, aiding selection, but does not explain semantics of many parameters (e.g., protocol, publishMode, autoRenew). Schema coverage is low (13%), so description partially compensates but insufficiently.

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?

Description clearly states the tool manages ports, auth, and certs with specific action-resource pairs (createPort, deletePort, etc.), distinguishing it from sibling tools like dokploy_server.

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?

No guidance on when to use this tool versus alternatives. It lists sub-actions but lacks context on prerequisites, scenarios, or differences from siblings.

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