coolify_update_application_config

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

Beyond annotations (readOnlyHint=false, idempotentHint=true), the description discloses two useful behavioral traits: 'PATCH semantics' (partial updates) and an audit trail ('Audit: coolify.application.config.update'). This adds context without contradicting annotations.

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 concise sentence, front-loaded with the main action and resource, followed by relevant details (config areas, PATCH semantics, audit). Every element earns its place and no filler is present.

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 15-parameter update tool without an output schema, the description covers the main scope and semantics. It could go deeper on preconditions (e.g., application must exist) or effects (e.g., triggers redeploy), but the given context plus schema descriptions provide enough for an agent to proceed safely.

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 baseline is 3. The description only lists broad categories (health check, resource limits, etc.) and does not add per-parameter meaning beyond what the schema already provides. The 'PATCH semantics' note indirectly implies optionality, but that is more behavioral than parameter-specific.

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 the specific verb 'Update' with resource 'application configuration' and enumerates key areas (health check, resource limits, replicas, ports, build settings). This clearly distinguishes it from sibling tools like coolify_create_application and coolify_update_database_config.

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 clearly indicates this is for modifying existing application configuration via 'Update' and 'PATCH semantics'. It does not explicitly name when not to use it or provide alternatives, but the context is unambiguous enough for an agent to differentiate from create/deploy/restart tools.

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