Coolify: Update application envs bulk

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

The annotations already disclose destructiveHint=true, idempotentHint=false, and readOnlyHint=false, so the bar is lower, but the description adds nothing beyond them. For a destructive bulk mutation, it is critical to know whether this replaces the entire env set or merges into it, and that is unstated. The "[UNIFIED]" prefix is unexplained jargon and does not compensate.

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?

It is a single sentence with no padding, which is structurally fine, but it is terse to the point of under-specification. The "[UNIFIED]" tag is noise an agent cannot act on, and the sentence stops well short of what a destructive bulk operation requires.

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 destructive bulk mutation with three undocumented required parameters and no output schema, the description is materially incomplete. It does not specify the shape of data, the replace-vs-merge semantics, or the effect on the running application after the update.

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 0%, so the description must carry the parameter meaning, and it does not. The three required parameters (site, uuid, data) are never mentioned, and the schema gives no clue about the expected structure of the data array (items: {}), so an agent cannot construct the payload from the description or the schema alone.

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 gives a specific verb and resource: "Bulk update environment variables for a Coolify application." The word "Bulk" implicitly distinguishes it from the single-variable sibling coolify_update_application_env, which fits the tool name. However, it never explicitly says how it differs from that sibling or from coolify_update_service_envs_bulk, so the differentiation must be inferred from the name alone.

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?

There is no guidance on when to use bulk rather than single-variable updates, no prerequisites (for example, whether the application must be stopped or redeployed), and no mention of alternatives. An agent must infer usage entirely from the name and the annotations.

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