coolify_deploy

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

With no annotations, the description must disclose behavioral traits. It only states the action without explaining side effects (e.g., triggers build, async nature, potential conflicts). The agent cannot infer if deployment is destructive or idempotent.

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 extremely concise (one sentence), but lacks structure. It does not front-load the most critical information (e.g., that multiple parameters can be used together). Conciseness is not a substitute for completeness.

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 4 parameters and no output schema or annotations, the description is woefully incomplete. It does not explain what 'deploy' means (e.g., build and deploy?), prerequisites (e.g., resource must exist), or what the tool returns (e.g., deployment ID).

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?

Although schema coverage is 100%, the description adds minimal value beyond the schema. It mentions 'uuid' and 'tag' but ignores 'pr' and 'force'. For example, explaining that 'force' rebuilds without cache would be helpful. The description fails to compensate for the schema's generic descriptions.

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 verb 'Deploy' and the resource 'resources', with identifiers 'by UUID or tag'. However, it omits the 'pr' parameter, which is also a valid identifier, slightly reducing completeness. Still, the core purpose is communicated.

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 on when to use this tool versus alternatives like coolify_start_application or coolify_restart_application. The description lacks context for decision-making, making it harder for the agent to choose correctly.

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