coolify_create_environment

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

No annotations are provided, so the description carries the full burden. It states '[WRITE]' indicating a mutation, but does not describe what happens after creation (e.g., whether it's automatically activated, or if it triggers any side effects). The description lacks details on permissions, idempotency, or error cases.

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 sentence that is concise and front-loaded with the '[WRITE]' marker. Every word is necessary, but it could be slightly more descriptive without losing conciseness.

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 has 2 required parameters, no output schema, and no annotations, the description is too sparse. It does not explain the response format, potential errors, or the relationship between environments and projects. The low complexity is offset by the lack of behavioral details.

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?

Both parameters are described in the schema (100% coverage), so the baseline is 3. The description does not add any additional meaning beyond what the schema already provides. The schema documents 'name' as 'Environment name (e.g. 'staging', 'production')' and 'project_uuid' as 'UUID of the project', which is sufficient.

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 starts with '[WRITE]' to indicate a mutation, and clearly states 'Create a new environment in a Coolify project'. The verb 'create' and resource 'environment' are specific. However, it does not differentiate from sibling tools like 'coolify_create_project' or 'coolify_create_application', which also create resources, but the target resource is distinct enough.

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 no guidance on when to use this tool versus alternatives. There is no mention of prerequisites (e.g., project must exist) or when not to use it. Siblings like 'coolify_list_environments' or 'coolify_get_environment' are not referenced for context.

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