Coolify: List services

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

Annotations already declare readOnlyHint=true, so safety is covered; the description adds real value by disclosing that output is truncated/compact unless include_details is set. It says nothing further about ordering, pagination, truncation limits, or what 'compact' actually drops, which is the main behavioral question an agent would have.

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?

Two tight sentences, with the default behavior and its override front-loaded in the first and second positions respectively. The "[UNIFIED]" tag adds little for a calling agent but costs only one token.

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 5-parameter tool with zero schema documentation and no output schema, the description covers only one optional boolean. An agent still cannot tell what 'site' means, how 'fields' and 'limit' are formatted, or what a compact record contains before calling.

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 description coverage is 0% across 5 parameters, so the description must compensate and it only explains include_details. The required 'site' parameter, plus 'name', 'limit' and 'fields' (both typed as strings, unusually), get no meaning, format, or accepted-value guidance anywhere.

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?

States a specific verb and resource ("List Coolify services") and adds the output-shape distinction (compact by default, full payloads with include_details). An agent can tell it apart from create_service or list_service_envs, but the description never contrasts it with other list endpoints such as coolify_list_applications or coolify_list_databases.

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 only usage guidance is an intra-tool toggle: "Use include_details=true for full Coolify payloads." There is no statement of when to reach for this tool versus the sibling list tools, and no prerequisite or scoping advice despite 'site' being required.

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