coolify_deploy

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

Annotations already communicate safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=true). The description adds context about operation mode, allowlist, and production guard policies, which is useful but does not explain deployment behavior (e.g., asynchronous process, return format).

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 concise sentence that immediately states the action and key constraints. It is well-structured, front-loaded, and contains no unnecessary words.

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?

The description is terse and, with no output schema, does not explain return values or post-deployment behavior. It includes policy constraints but lacks details on async behavior or error scenarios, leaving some gaps for an agent making full use of the tool.

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 all parameters are already documented with descriptions. The tool description adds no additional parameter meaning beyond the schema, justifying the baseline score of 3.

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 ('Deploy a resource') with a specific verb and resource, differentiating it from create/update/cancel siblings. However, it does not explicitly contrast with related actions like 'start' or 'restart', so it lacks explicit sibling differentiation.

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 provides no guidance on when to use this tool versus alternatives like coolify_start, coolify_restart, or coolify_cancel_deployment. It only mentions policy constraints, which is a caveat rather than usage direction.

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