coolify_import_database

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

With zero annotations the description carries the full burden and does well: the [DESTRUCTIVE] prefix warns of data loss, 'runs in the background' plus the named polling tool discloses async behavior, and the token requirement for server sources is stated. It stops short of saying whether existing objects in the target database are overwritten or that the action is irreversible.

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?

Three short sentences, with the destructive warning and the core action front-loaded and the async-poll and prerequisite notes trailing in priority order. No filler.

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?

Covers what an agent needs to invoke it safely for an 11-parameter async mutation with no output schema: destructive nature, background execution, polling target, and a source-specific prerequisite. A note on failure/overwrite semantics for the target database would close the remaining gap.

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 the parameter documentation baseline is already met. The description adds genuine value beyond the schema by linking source selection to a permission prerequisite (deploy token for source=server) and by naming the required follow-up poll, which no individual property description conveys.

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?

Specific verb (restore/import) plus resource (a standalone database) plus the three accepted backup origins. The word 'standalone' distinguishes it from coolify_import_service_database, so an agent can pick correctly without opening either schema.

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?

It states the operation's context (restoring a backup from S3, a server path, or an earlier upload) and routes the agent to coolify_get_database_import for polling. It also flags the deploy-token prerequisite for source=server, though it never explicitly contrasts itself with coolify_import_service_database.

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