coolify_list_services

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

No annotations are provided, so the description carries full responsibility for behavioral disclosure. The description does not mention whether the operation is read-only, safe, or if there are rate limits, pagination, or any side effects. It is completely opaque about behavior, which is insufficient for an AI agent.

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 of three words, with no extraneous information. It is maximally concise and front-loaded. Every word 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?

Given the simplicity of the tool (no parameters, no output schema), the description is short but lacks completeness. It does not clarify what 'services' covers or how it differs from other listing tools. Without this, an agent may not correctly identify when to use this tool, especially when multiple list tools exist.

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?

There are zero parameters, so the input schema provides no information. The description adds the context that all services are listed, which is a minimal but acceptable addition. Following the rubric, baseline for 0 parameters is 4.

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 'List all services' clearly states the action (list) and resource (services). It is a specific verb+resource pair. However, it does not elaborate on what constitutes a 'service' in Coolify, which is somewhat ambiguous given sibling tools for applications, databases, etc. Still, the name and description are enough to distinguish it as a listing operation for a specific resource type.

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_list_applications or coolify_list_databases. It does not specify prerequisites, exclusions, or typical use cases. The agent has no help in deciding between related list tools.

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