coolify_list_envs

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. While 'List' implies a read-only operation, the description does not explicitly state the absence of side effects, permissions required, rate limits, or pagination behavior. It is adequate for a simple list but adds no value beyond the tool name.

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 is front-loaded, concise, and contains no unnecessary words. Every word contributes to the purpose.

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 there is no output schema, the description does not explain the return format (e.g., array of key-value pairs, JSON object). It also does not mention whether the list is flat or nested, or how errors are handled. For a simple list tool, this is minimally adequate but leaves gaps for an agent to understand the full response.

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 100% (the only parameter 'uuid' has a description: 'UUID of the application'). The description reinforces that the uuid refers to an application but does not add new meaning such as how to obtain the UUID or format constraints beyond what the schema's pattern and length constraints already provide.

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 environment variables for a Coolify application' uses a specific verb ('List') and clearly identifies the resource ('environment variables') and the context ('for a Coolify application'). This distinguishes it from sibling tools like coolify_list_database_envs (database envs) and coolify_list_environments (environments, not env vars).

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 such as coolify_create_env, coolify_update_envs_bulk, or coolify_list_database_envs. It does not mention prerequisites, context, or exclusions, leaving the agent to infer usage from the name alone.

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