coolify_update_application

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

With zero annotations, the description carries full burden for behavioral disclosure. It only states '[WRITE]' to hint mutation but does not explain merge vs. overwrite behavior, required fields beyond uuid, side effects of instant_deploy, or what happens to omitted fields. This is insufficient for a complex mutation tool.

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 very brief (7 words including [WRITE]). While it wastes no words, it is underspecified for a tool with 17 parameters. Conciseness is achieved at the cost of completeness, making it minimally adequate.

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 high complexity (17 params, nested object, no output schema), the description is incomplete. It does not explain return values, behavior when only uuid is provided, or how instant_deploy interacts with other fields. The agent lacks essential context for correct invocation.

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% with descriptions for all 17 parameters, so the baseline is 3. The description adds no extra meaning beyond what the schema already provides (e.g., it doesn't explain how custom_fields override or supplement other fields). The agent must rely solely on the schema.

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 clearly states the action ('Update') and resource ('configuration of a Coolify application'), and the [WRITE] prefix indicates mutation. However, it does not differentiate from siblings like coolify_create_application or coolify_delete_application, leaving ambiguity for the agent.

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?

No guidance on when to use vs. alternatives. It does not specify prerequisites (e.g., application must exist), when to prefer create over update, or mention that instant_deploy triggers a deployment. The description is silent on usage context.

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