Coolify: Start application

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

Annotations already declare readOnlyHint=false, destructiveHint=true, and idempotentHint=false, so the safety profile is known. The description adds useful context that starting actually triggers a new deployment, which explains the destructive/non-idempotent nature, but says nothing about what gets replaced, whether the running container is destroyed, or required permissions.

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?

Two short sentences, front-loaded with the action, with no wasted wording. The '[UNIFIED]' prefix is unexplained noise that does not help the agent.

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 destructive, non-idempotent mutation with four parameters at 0% schema coverage and no output schema, the description should at minimum explain the boolean flags and what the deployment trigger affects. As written it leaves the agent guessing about the most consequential options.

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 0% across four parameters, and the description explains none of them. In particular the 'force' and 'instant_deploy' flags are left completely opaque, and even 'site' vs 'uuid' semantics are not clarified beyond the schema types.

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 gives a specific verb and resource ('Deploy/start a Coolify application') and adds that it triggers a new deployment, so the agent can tell it is the start operation rather than stop or restart. It stops short of explicitly naming the sibling alternatives (coolify_restart_application, coolify_stop_application), so it is clear but not fully differentiated.

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?

There is no statement of when to use this versus coolify_restart_application or coolify_start_service, and no preconditions (e.g., application must already exist, must be stopped). The only hint is the word 'start' in the name and 'new deployment' in the text, leaving selection to inference.

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