Update Application Environment Variable

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

Description adds that Coolify matches by key name and updates existing env var. Annotations idempotentHint=true and readOnlyHint=false are consistent. However, it does not address behavior if key does not exist or error handling. Moderate transparency.

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 sentences front-loaded with core purpose and matching logic. No superfluous text. Efficiently conveys essential information.

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?

No output schema, and description does not explain return value or error conditions. Schema provides detailed parameter info, but the tool's result or failure modes are missing. Adequate given parameter descriptions but incomplete for operations.

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 has 100% coverage, so baseline 3. Description adds context on key matching but does not significantly enhance understanding of other parameters like reveal, is_preview, etc. Adequate but not exceptional.

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 clearly states the tool updates an existing environment variable on an application, distinguishing it from create/delete env var siblings. It specifies matching by key name and that key and value are required.

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 does not explicitly state when to use this tool vs alternatives like bulk env operations. It implies usage for single env update but provides no when-not or exclusion criteria.

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