coolify_create_application_private_deploy_key

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

No annotations are provided, so the description must disclose behavioral traits. It states 'create' (write operation) but does not mention side effects like deployment triggers, required permissions, or error states (e.g., invalid key). It lacks transparency.

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 of 11 words, fully front-loaded, with no redundant information. Every word earns its place.

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 the tool has 10 parameters, 8 required, and no output schema, the description is too sparse. It does not explain prerequisites (e.g., existing project, server, private key), return value, or how optional parameters like 'name' or 'instant_deploy' affect behavior. Incomplete for safe autonomous use.

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 baseline is 3. The description adds context ('private repository using SSH deploy key') that reinforces the purpose of private_key_uuid and git_repository, but the schema already has clear descriptions for each parameter. No significant additional meaning beyond 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 tool creates an application from a private repository using an SSH deploy key. This verb+resource+method is specific and distinguishes it from siblings like coolify_create_application_public or coolify_create_application_private_github.

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. With many sibling tools for creating applications (public, private GitHub, Dockerfile, etc.), the description should indicate prerequisites or context, e.g., 'use when you have a private SSH key added via create_private_key'.

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