Coolify: Create postgresql

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

Annotations already declare readOnlyHint=false and destructiveHint=true, so the safety profile is covered; the description adds nothing beyond that. It does not explain what is actually provisioned, whether deployment is immediate, what instant_deploy does, permission requirements, or consequences of creation — all valuable context 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?

A single front-loaded sentence with the verb and resource up front, and no padding. The only wart is the meaningless '[UNIFIED]' tag, and the brevity reflects under-specification rather than actual conciseness quality.

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 creation tool with seven undocumented parameters and no output schema, the description supplies none of the operational context an agent needs — no prerequisites, no parameter meanings, no indication of what is returned or what side effects occur.

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?

Seven parameters with 0% schema description coverage, and the description names none of them. It gives no hint about the meaning of instant_deploy, name, description, or how the required UUIDs and environment_name relate to existing Coolify entities.

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 states a specific verb and resource: creating a PostgreSQL database on Coolify, which an agent can readily distinguish from sibling create tools for MySQL, MariaDB, MongoDB, Redis, or applications. The '[UNIFIED]' prefix is unexplained noise but does not obscure the purpose.

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 this tool versus alternatives, and no mention of prerequisites such as the need for an existing project, server, and environment (all required parameters). The agent must infer that project_uuid, server_uuid, and environment_name must reference pre-existing resources.

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