coolify_start_application

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

With no annotations, the description carries full burden. It does not disclose whether the operation is asynchronous, if it requires specific permissions, or what state changes occur. The effects of the 'force' and 'commit' parameters are only briefly explained in the schema, not in the description.

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 extremely concise (three words) but lacks essential information. It is not front-loaded with critical context; important details about the tool's behavior and parameters are omitted. Brevity here sacrifices usefulness.

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 no output schema and no annotations, the description is incomplete. It does not explain return values, error scenarios, or how the tool fits into the workflow. For a tool with three parameters, more context is needed to ensure correct usage.

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 does not add meaning beyond the schema; the parameter descriptions are adequate but minimal. The description 'Start/deploy an application' gives no additional context for parameters like 'uuid' or 'force'.

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 tool's function as 'Start/deploy an application'. It uses a verb and resource, and distinguishes it from sibling tools like 'coolify_stop_application' or 'coolify_restart_application'. However, it could be more specific about the deployment aspect differentiating it from 'coolify_deploy'.

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 is provided on when to use this tool versus alternatives like 'coolify_deploy' or 'coolify_start_database'. There is no mention of prerequisites, such as the application needing to exist or be in a stopped state. The description lacks context for decision-making.

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