Coolify: Create mariadb

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and idempotentHint=false, so the safety profile is covered structurally. The description adds nothing beyond the one-line purpose: it does not explain what instant_deploy does, what happens on failure, or whether re-creating with the same name duplicates or errors.

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 single sentence is short and front-loaded, which is good, but the '[UNIFIED]' prefix is unexplained noise that contributes no meaning to an agent. There is nothing else to trim, but also nothing else of value.

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, non-idempotent, 7-parameter creation tool with zero schema descriptions and no output schema, a one-line description leaves the agent without the information needed to call it correctly or safely. Completeness is inadequate relative to the tool's complexity.

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% across 7 parameters, so the description carries full burden for explaining site, project_uuid, server_uuid, environment_name, name, description, and instant_deploy. It mentions none of them, including the non-obvious instant_deploy defaulting to false.

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 plus resource ('Create a MariaDB database') and naming the database engine distinguishes it from siblings like coolify_create_mysql and coolify_create_postgresql. It stops short of stating scope (e.g. per-site/per-environment), but the core action is unambiguous.

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 when-to-use or when-not-to-use guidance, no mention of prerequisites (project, server, environment must exist), and no comparison to the sibling database-creation tools. The agent must infer everything from parameter names.

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