List environment variables

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

Beyond the readOnlyHint annotation, the description discloses that values are masked to keep secrets out of the conversation, explains the masking format, and reveals the server-side requirement (COOLIFY_ALLOW_REVEAL=1) for plaintext. This is valuable behavioral context that annotations do not provide.

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?

Three sentences with no filler: it front-loads what is listed, then the masking rule, then the reveal caveat. Every sentence earns its place and the most safety-critical guidance is placed at the end without being buried.

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?

There is no output schema, so the description compensates by explicitly listing the output fields and flag names. It also covers the important masking behavior and the security-critical reveal condition. The schema covers all parameters, so no essential calling information is missing.

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 coverage is 100%, so the schema already documents all parameters. The description adds context about reveal behavior but does not add new meaning to the parameters themselves; it correctly relies on the schema for parameter semantics.

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 names a specific verb ('List') and a precise resource ('environment variables of an application or service'), and explicitly enumerates the returned fields (key, uuid, flags). This clearly distinguishes it from sibling tools like list_applications, set_envs, and delete_env.

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?

It provides clear usage context: this is a read-only listing operation, and it gives an explicit when-not instruction for reveal ('avoid it unless the user explicitly needs a value'). It does not explicitly name alternatives such as set_envs or delete_env, but the read-only framing makes the distinction clear.

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