coolify_create_database_env

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

With no annotations provided, the description bears the full burden of behavioral disclosure. It only includes a '[WRITE]' tag implying mutation but does not describe what happens on success (e.g., returns the created variable?), error conditions, idempotency (does it overwrite existing keys?), or authentication/rate-limit considerations. The behavioral information is minimal.

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 plus a '[WRITE]' tag, making it very concise. However, it lacks structure (e.g., no separate sections or additional details). While it is not verbose, a few more words could improve clarity without sacrificing 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?

The tool has 8 parameters, no output schema, and is a mutation operation. The description only says 'Create a new environment variable for a Coolify database' without explaining return values, error scenarios, or any side effects. Given the complexity (multiple boolean flags, optional comment), this is notably incomplete.

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%, so baseline is 3. The description does not add any additional meaning beyond the schema; it merely restates the overall action. The schema already fully describes each parameter with names, types, and descriptions. The description adds no extra semantic value.

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 verb ('Create') and resource ('environment variable for a Coolify database'), and the '[WRITE]' prefix further clarifies it's a mutating operation. It distinguishes itself from sibling tools like coolify_delete_database_env (delete), coolify_update_database_envs_bulk (bulk update), and coolify_create_env (generic env creation) by specifying it's database-specific.

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?

No guidance is provided on when to use this tool versus alternatives like coolify_create_env or coolify_create_service_env. It does not mention prerequisites (e.g., needing a database UUID), nor does it explain when not to use it. The description lacks any usage context.

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