coolify_start_database

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

No annotations are provided, so the description carries the behavioral burden. The '[WRITE]' prefix explicitly signals a write/mutative operation, which is appropriate for starting a database. It does not disclose error conditions (e.g., starting a running database) or state transitions, but for a simple start action this is reasonable.

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 a single very short sentence with a useful '[WRITE]' prefix, which is concise and front-loaded. It earns its place but could slightly expand on what 'start' entails (e.g., initiates the database service).

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 is a simple start action with one parameter and no output schema, the description is minimally complete. However, for a write operation, it could mention idempotency or error behavior (e.g., 'no effect if already running').

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 schema already documents the required 'uuid' parameter as 'UUID of the resource'. The description adds no further parameter meaning, which is acceptable baseline for full coverage.

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 specifies 'Start a stopped Coolify database', which clearly identifies the verb (start) and resource (Coolify database), distinguishing it from siblings like 'stop_database' and 'restart_database'. However, it does not differentiate from 'start_service' or 'start_application' explicitly.

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?

The description states the tool is for starting a stopped database, implying when to use it, but provides no guidance on when not to use it (e.g., if already running) or alternatives like restart_database.

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