coolify_update_database

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

No annotations are provided, so the description carries the behavioral transparency burden. The '[WRITE]' prefix indicates a mutating operation, which aligns with 'Update' in the description. However, the description doesn't disclose whether changes are immediately applied, require a restart, what happens to unspecified fields (default persistence vs reset), or whether any authorization properties are needed. For a mutation tool without annotations, this is adequate but not comprehensive. It doesn't contradict any annotations since none exist.

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 sentence with no fluff. It immediately communicates the action (Update) and resource (configuration of a Coolify database). The '[WRITE]' prefix adds a tiny bit of extra context without becoming verbose. Every word earns its place, making it as concise as possible for a description of this tool.

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?

The tool has 9 parameters (including one required), no output schema, and no annotations. For a moderately complex update tool, the description is too brief. It doesn't mention what the return value looks like (which is partially excused by no output schema), nor does it clarify that the uuid parameter is essential to identify which database to update. The agent might need to infer that updating a non-existent database could fail. Given the complexity and lack of additional schema/annotation support, a score of 3 is appropriate—minimally adequate but with clear gaps.

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%, meaning every parameter already has a description. The description doesn't add any new meaning beyond the schema—it simply states 'Update configuration of a Coolify database'. With full schema coverage, the baseline score is 3, and since no additional context is provided (e.g., which parameters are commonly used together, or that uuid identifies the target), the score remains 3.

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 uses a specific verb 'Update' and resource 'configuration of a Coolify database', which clearly states the tool's purpose. It distinguishes the tool from siblings like coolify_create_database, coolify_delete_database, and others that perform different actions on databases. However, the prefix '[WRITE]' adds context about the operation type, which is useful but not strictly necessary for clarity.

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 provides no guidance on when to use this tool versus alternatives like coolify_create_database (for new databases) or the stop/start database tools. It doesn't mention prerequisites (e.g., the database must exist), nor does it note that other update tools exist for specific aspects (e.g., update_database_envs_bulk, update_database_storage). The agent must infer usage from context alone.

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