coolify_list_services

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

The description discloses that the tool returns a summary of services with specific fields, which is useful. However, it does not explicitly state that the operation is read-only or has no side effects. Since no annotations are provided, the description carries the full burden; it is adequate but could be more transparent about the behavioral safety profile.

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 sentence that front-loads the purpose, includes the return summary in parentheses, and contains no unnecessary words. Every part earns its place.

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 simple list tool with no parameters and no output schema, the description is complete. It states what is listed, the scope (all services), and the fields returned. No additional context is needed.

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?

The input schema has no parameters, so the description's job is to explain the tool's behavior. It does so by indicating the tool returns 'all services' and lists the summary fields. This adds value beyond the empty schema. With 0 parameters, a baseline of 4 is appropriate.

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 purpose: 'List all services managed by Coolify' with a specific verb 'List' and resource 'services'. It distinguishes from sibling tools like 'coolify_list_applications' and 'coolify_list_databases' by naming the resource category. It also specifies the return fields (uuid, name, status, service_type), adding precision.

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 explicit guidance on when to use this tool vs alternatives. The tool name and resource category implicitly differentiate it from sibling list tools, but the description does not direct the agent to use this for services and not for applications/databases, nor does it mention any conditions or side effects.

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