coolify_create_server

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

No annotations exist, so the description carries full burden. The description explicitly labels this as a '[WRITE]' operation and notes the SSH private key requirement, which signals the type of credentials needed and that this is a mutation. It could mention that the operation likely creates a persistent record, but the bracket tag and key requirement provide reasonable transparency.

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 a single, focused sentence with an essential parenthetical note. Every word adds value, and there is no redundant phrasing.

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 creation tool with 8 parameters and no output schema, the description is nearly complete. It explains the action and the critical prerequisite (SSH private key). The only minor gap is that it doesn't hint at the response (e.g., returns the created server object), but since there is no output schema, this is acceptable.

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 100%, so the schema already documents all 8 parameters. The description adds no additional semantic value beyond the existing parameter descriptions, which is sufficient for a baseline of 3.

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 action ('Create') and the resource ('Coolify server'), and the parenthetical note about requiring an SSH private key adds important context. It distinctly differentiates this tool from siblings like coolify_list_servers, coolify_get_server, and coolify_delete_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?

The description implies when to use this tool (to create a server) but offers no guidance on when not to use it or alternatives. With many sibling tools for other resources, it doesn't help the agent decide between creating a server vs. other resources.

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