coolify_update_database_envs_bulk

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

No annotations are provided, so the description must fully disclose behavior. It labels the operation as '[WRITE]' and notes 'creates or updates', but fails to clarify whether the bulk update is additive (merges) or replaces all existing environment variables. It also does not mention idempotency, partial failure handling, or whether unchanged variables are preserved. This is a significant gap for a mutation tool.

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, concise sentence that front-loads the action type '[WRITE]' and includes the critical upsert clarification. Every word is necessary and no information 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?

Given the lack of annotations and output schema, the description is too brief. It does not explain the bulk semantics (replacement vs. merge), error conditions, limits, or behavior for missing keys. It also fails to differentiate from sibling tools beyond the resource mention, leaving the agent with uncertainty about consequences of invocation.

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 coverage is 100% – both parameters (uuid, envs) have descriptions. The description adds no parameter-level details beyond what the schema already provides (e.g., 'Array of environment variables to set' and 'UUID of the database'). Baseline 3 is appropriate since the schema does the heavy lifting.

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 ('update'), the resource ('environment variables for a Coolify database'), and includes the upsert behavior ('creates or updates'). The name itself indicates 'bulk', and the description distinguishes it from single env creation (coolify_create_database_env) and the generic coolify_update_envs_bulk by specifying 'for a Coolify database'.

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 explicit guidance on when to use this tool versus alternatives (e.g., coolify_create_database_env for a single variable, or coolify_update_envs_bulk for non-database resources). There are no prerequisites, exclusions, or context hints. Usage is only implied by the resource name.

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