coolify_start_application

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

No annotations are provided, so the description carries the full burden of disclosure. It only states 'Start' and '[WRITE]', which implies mutation but does not explain side effects (e.g., changing status, requiring permissions, or impact on deployments). The description is too brief to give an agent confidence about what happens.

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 (5 words plus a tag), but it is borderline under-specified. It is front-loaded with the tag but lacks necessary details. Every sentence is earned, but the overall length may leave gaps.

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 low complexity (1 param, no output schema), the description is minimally adequate. It covers the core action but does not mention error conditions (e.g., what if the application is already running) or the return value. It is complete enough for a simple tool but could be improved.

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% with the uuid parameter already described. The description adds the context of starting an application but does not add meaning beyond the schema. Baseline 3 is appropriate per the rubric.

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 'Start' and the resource 'Coolify application', with the prefix '[WRITE]' indicating it's a write operation. It distinguishes itself from sibling tools like coolify_stop_application and coolify_restart_application by specifying it starts a stopped application.

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 vs alternatives (e.g., coolify_restart_application). No prerequisites or context about the application needing to exist or be stopped are provided. The description does not help the agent decide between similar tools.

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