coolify_create_server

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

The description states creation but provides no details about side effects, required permissions, or post-creation behavior. With no annotations, the agent is left uninformed about aspects like immediate validation or state changes.

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 short sentence, which is concise but lacks substance for an 8-parameter creation tool. It earns its place but could include more essential context without becoming verbose.

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?

Without an output schema, the description should mention what is returned (e.g., server ID or status). It also omits prerequisites like private key setup. The tool has 8 parameters and no output guidance, making the description incomplete.

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 parameter context beyond the schema, but the schema already documents all 8 parameters adequately. No additional value from description.

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 'Create/add a new server' is clear and specific, using a verb+resource format. It distinguishes from sibling tools like update, delete, and validate, but does not elaborate on the scope or type of server.

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 when-to-use or alternative guidance is provided. The description does not clarify when to choose this tool over others like coolify_update_server or coolify_validate_server, leaving the agent without context for selection.

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