Create Application — Private Repository (GitHub App)

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

The description adds useful behavioral context such as the audit note for the 'reveal' parameter and a safety warning for 'instance'. However, it does not disclose whether creation triggers an automatic deployment or if the operation is idempotent, beyond what annotations indicate.

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 three sentences long and delivers the core purpose, prerequisite, and a key safety note with no wasted words. It is front-loaded and efficient.

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 complexity (14 parameters) and lack of output schema, the description covers the main purpose and several key parameters. However, it does not explain return values, side effects (e.g., whether deployment starts), or how the result is used.

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%, so baseline is 3. The description adds significant value for several parameters: explains the safety rationale for 'instance', the limitation of 'domains', and the auditing for 'reveal'. This goes beyond the schema definitions.

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 ('Create an application') and the specific method ('from a private Git repository using a GitHub App'). This differentiates it from sibling tools like coolify_create_application_deploykey or coolify_create_application_public.

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 mentions a prerequisite ('Requires a GitHub App already configured in Coolify') and implies the tool is for private repos. However, it does not explicitly state when to avoid using it or provide direct comparison to siblings with similar purposes.

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