Create Application — Private Repository (Deploy Key)

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

Annotations already indicate it's a write operation (readOnlyHint=false). The description adds prerequisite context but does not discuss idempotency (which is false per annotations) or failure modes. It avoids contradiction but adds minimal behavioral detail beyond annotations.

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 sentences, no filler. Purpose is stated upfront, followed by prerequisite instructions. Every sentence adds value and is well-structured for quick understanding.

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 creation tool with 14 parameters and no output schema, the description adequately covers core behavior and prerequisites. It does not describe return values or error handling, but the schema and context provide enough for informed use. One minor gap: missing explanation of what is returned (e.g., created app details).

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?

The schema covers 100% of parameters with descriptions, so baseline is 3. The tool description does not add extra parameter-level insight; it only summarizes the purpose. No additional value is provided beyond standard schema documentation.

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 from a private Git repository with a deploy key') and the specific mechanism (deploy key), differentiating it from siblings like coolify_create_application_public or coolify_create_application_githubapp.

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 explicitly states when to use this tool (private repo with deploy key) and lists prerequisites (private key in Coolify and public key on GitHub), referencing related tools. It does not explicitly state when not to use or mention alternatives, but the context is clear.

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