delete_environment

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

The description discloses the critical behavior that the confirm parameter may be required based on an environment variable. No annotations are provided, so the description carries full burden. It could be improved by noting that the action is irreversible, but the disclosed conditional requirement is valuable.

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 two sentences with no wasted words. It front-loads the main action and then adds the essential conditional guidance efficiently.

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?

Given the simple nature of a delete tool, the description covers the primary action and a key usage condition. It could mention irreversibility or permissions, but the combination of schema coverage and description is largely complete.

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 schema already documents all parameters. The description adds context about the COOLIFY_REQUIRE_CONFIRM environment variable, which enhances understanding of the confirm parameter's condition, going beyond what the schema provides.

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 'Delete' and resource 'environment', distinguishing it from siblings like create_environment, get_environment, and list_environments.

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 mentions a conditional requirement (COOLIFY_REQUIRE_CONFIRM env var) that affects when the confirm parameter is needed, providing clear context. However, it does not explicitly state when to use this tool versus alternatives, such as other delete tools.

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