Coolify: Create mysql

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

Annotations already declare readOnlyHint=false, destructiveHint=true, and idempotentHint=false, so the safety profile is covered. The description adds nothing beyond that: it does not say what immediately happens on creation, what instant_deploy changes, whether the deploy is asynchronous, or what credentials/identifiers are returned for the new database.

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?

One short sentence with no filler, and the verb is front-loaded. However, the brevity is achieved by omitting everything rather than by tight editing, and the unexplained "[UNIFIED]" tag is dead weight.

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 non-idempotent, destructive, seven-parameter mutation with zero schema documentation and no output schema, this description is far too thin. An agent cannot tell what side effects to expect, whether a failed call leaves partial state, or what the response contains.

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% and the description names none of the seven parameters. Critical semantics — what 'site' means versus 'project_uuid'/'server_uuid', and what 'instant_deploy' toggles — are documented nowhere.

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 ("Create a MySQL database") and names the platform (Coolify), which lets an agent distinguish it from the sibling create_mariadb, create_postgresql, create_mongodb, and create_redis tools. The "[UNIFIED]" prefix is unexplained jargon that adds no discriminating information.

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 guidance, no statement of prerequisites, and no conditions distinguishing this from the other database-creation siblings beyond the engine name. An agent is left to infer that four required identifiers (site, project_uuid, server_uuid, environment_name) must already exist, with no hint about how to obtain them.

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