coolify_list_service_envs

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

No annotations are provided, so the description must carry the behavioral transparency burden. It only states 'list', implying a read operation, but does not confirm read-only nature, permissions required, or any side effects. The brief description does not sufficiently disclose behavior.

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 with zero waste, making it concise. However, it is perhaps too brief for a tool that could benefit from a bit more context. Nevertheless, it is appropriately sized for its simplicity.

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?

Without an output schema, the description should explain what is returned (e.g., list of environment variable objects). It fails to mention return format, pagination, or required permissions. This lack of completeness makes it less helpful for agents.

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 100% description coverage for the single 'uuid' parameter, so the description does not need to add additional meaning. It adds no extra context beyond the schema, earning the baseline score of 3.

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 environment variables for a service' uses a specific verb and resource, clearly indicating the action and target. It effectively distinguishes from sibling tools like create, update, delete operations, and from similar tools for applications (e.g., coolify_list_application_envs) by specifying 'service'.

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_list_application_envs. It does not mention prerequisites, scope, or when to choose this over other listing tools.

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