deploy_coolify_application

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

No annotations provided. The description simply says 'Deploy a Coolify application' without explaining whether the deployment is asynchronous, idempotent, or what triggers it. Completely insufficient behavioral info.

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?

Extremely short but at the cost of informativeness. It is a single generic sentence that does not earn its place; it provides minimal guidance.

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 tool with one parameter and many similar siblings, the description is severely incomplete. It does not explain the deployment process, prerequisites, or return behavior. Substantial gaps remain.

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 coverage is 100% (one parameter with description 'Application UUID'). The description does not mention the parameter or add any meaning beyond the schema. Baseline 3 is inappropriate because the description adds zero value.

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?

Description states action (deploy) and resource (Coolify application). However, it lacks specificity to distinguish from siblings like 'start_coolify_application' or 'restart_coolify_application', which could be confused.

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. For example, when should an agent use 'deploy' instead of 'start' or 'restart'? Missing exclusions or context.

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