Delete Service Environment Variable

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and idempotentHint=true. The description adds 'docker-compose apps' context but does not disclose additional behaviors such as error handling, confirmation prompts, or effects on dependent resources. The annotations carry most of the burden, and the description provides marginal extra 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?

The description is a single sentence of 9 words, no fluff. It is front-loaded with the action. However, it could optionally include a brief note about instance selection or idempotency without harming conciseness.

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 simple delete tool with well-annotated safety profiles and no output schema, the description covers the essential purpose. It lacks details on return value or side effects, but given the tool's simplicity, it is mostly complete. A 5 would require mention of idempotency or behavior on missing env.

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%, so the input schema fully documents all parameters. The tool description does not provide any additional semantic context beyond 'Remove an environment variable', so it adds no value over the schema. Baseline 3 is appropriate.

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 'Remove an environment variable from a Coolify service (docker-compose apps).' The verb 'Remove' and resource 'environment variable' are specific, and the parenthetical distinguishes it from other Coolify tools targeting different resource types, like coolify_delete_app_env for application 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 implies the tool is for deletion of a service env var, but it does not explicitly state when to use this tool over alternatives (e.g., coolify_delete_app_env) or provide prerequisites or exclusions. Usage is clear from context but lacks explicit guidance.

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