coolify_create_project

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

The description only states 'Create a new project' without disclosing any behavioral traits beyond the obvious mutation. Since no annotations are provided, the description carries the full burden but fails to mention side effects, idempotency, required permissions, or success/failure behavior.

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 that is concise and front-loaded with the action. It earns its place by stating the purpose, but the extreme brevity sacrifices completeness. A slightly more informative sentence would not hurt conciseness.

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 moderate complexity and many sibling tools, the description is too terse. It does not mention return values, success indicators, or any post-creation steps. Without an output schema, agents are left guessing about the result of a project creation.

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 input schema has 100% coverage with descriptions for both parameters ('Project name', 'Project description'). The tool description adds no additional semantic context, so a baseline score of 3 is appropriate as the schema already provides necessary information.

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 'Create a new project', specifying the verb and resource. While it distinguishes from sibling tools by using 'project' as the resource, it lacks additional context about what creating a project entails, such as whether it sets up any infrastructure or has prerequisites.

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 creating an environment or application. There is no mention of workflow order, such as needing to create a project before other resources.

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