coolify_create_server

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

No annotations are provided, so the description carries the full behavioral burden, yet it only discloses the SSH key requirement. It says nothing about required permissions, whether the server is validated/connected on creation, whether instant_validate triggers a remote SSH probe, what happens on duplicate IPs, or whether the operation is reversible.

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 single sentence is front-loaded with the action and contains no filler. It is arguably too terse for a nine-parameter mutation tool, but nothing in it is wasted.

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 write tool with no annotations, no output schema, and nine parameters, the description is far too thin. An agent gets no picture of side effects, prerequisite lookups (private key creation), or what the call returns, leaving meaningful gaps.

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 every parameter is already documented, including the deprecated is_build_server and server_role enum. The description adds no extra meaning (e.g., that private_key_uuid should come from coolify_list_private_keys), so the baseline 3 applies.

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 states a specific verb and resource ('Create a new Coolify server'), which cleanly separates it from siblings like coolify_update_server, coolify_delete_server, and coolify_list_servers by verb alone. It does not explicitly name or contrast with those siblings, so it stops short of a 5.

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?

Beyond the 'requires SSH private key' precondition, there is no guidance on when to choose this tool versus coolify_validate_server or coolify_update_server, nor any note about obtaining the key UUID via coolify_list_private_keys. The [WRITE] tag implies mutation but gives no workflow context.

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