Create Application Environment Variable

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

Annotations indicate a write operation and no idempotency. The description adds safety context by requiring explicit instance specification to avoid accidental writes to production. It does not detail rate limits or auth, but the annotations already cover the basic behavioral profile.

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 with no redundancy. The first sentence states the purpose, the second adds essential guidelines. Every word earns its place.

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 tool with no output schema and 8 parameters, the description is reasonably complete. It might have mentioned that env var changes take effect on redeploy, but the core information is present.

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?

All 8 parameters have schema descriptions (100% coverage), so the tool description adds minimal new meaning. The note about secrets origins adds indirect value for the 'value' parameter, but overall the schema does the heavy lifting.

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 verb 'Add' and the resource 'new environment variable to an application', distinguishing it from sibling tools like coolify_bulk_create_app_envs. The additional note about secrets does not obscure the primary purpose.

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 clear context: it is for single env var creation and advises against using for secrets (use BWS). However, it does not explicitly state when to use this tool over alternatives like the bulk versions.

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