coolify_set_environment_variables

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

Annotations already convey that this is a write operation (readOnlyHint=false) and idempotent. The description adds critical context: values are never returned in the response and the feature is disabled by default unless an environment variable is set. This enhances safety understanding beyond the structured annotations.

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 three sentences with no fluff. It front-loads the core purpose, then includes the critical configuration caveat and a clear privacy note, each earning its place.

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 bulk write operation with no output schema, the description covers the key safety aspects (default disabled, values never returned) and the operational scope. It doesn't explicitly mention idempotency or overwrite behavior, but the annotations cover idempotency, and the schema covers parameter validation. Sibling tools are reasonably differentiated.

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?

The input schema already provides descriptions for all parameters (100% coverage), including the variables array constraints (1-50) and resource_type enum. The description does not add new parameter-specific semantics beyond what the schema conveys, so a baseline of 3 is appropriate.

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 ('Set multiple environment variables'), the target ('on a resource'), and the scope ('in bulk (1-50)'). It also distinguishes itself from the sibling 'coolify_set_environment_variable' by explicitly indicating bulk operations.

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 bulk (1-50) phrasing implies use for multiple variables, and the singular sibling tool covers single-variable cases. The 'DEFAULT DISABLED — COOLIFY_ALLOW_ENV_WRITE must be true' note provides an important prerequisite and condition for use, effectively guiding when the tool can be invoked.

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