coolify_delete_database_env

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 includes a '[DESTRUCTIVE]' tag, which hints at the operation's nature, but it does not disclose whether the operation is irreversible, what happens to the database, or that confirmation is required. The confirm parameter is present in the schema but not mentioned in the description.

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 very concise at one sentence, which is good for front-loading. However, it lacks structure and does not use the available space to add useful information. It is not overly verbose, but it is too sparse to be considered well-structured.

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 3 parameters, no output schema, and many sibling tools, the description is incomplete. It does not explain the return value, how to interpret the confirmation parameter, or how this tool differs from similar ones like coolify_delete_env. The context signals suggest a need for more detail, but the description provides only a single line.

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 100%, so the baseline is 3. The description adds no additional meaning beyond what the schema already provides. For example, it does not explain the purpose of each parameter or provide context for their values.

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: 'Delete an environment variable from a Coolify database'. It uses a specific verb and resource, and the mention of 'from a Coolify database' distinguishes it from sibling tools like coolify_delete_env (which might delete from other contexts). However, it does not elaborate on the exact inputs or scope, which could be more precise.

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 vs alternatives. For example, there is no mention of prerequisites (e.g., needing the database UUID and env UUID), when to prefer this over coolify_update_database_envs_bulk, or when not to use it. The description is purely declarative.

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