delete_envs

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

With no annotations provided, the description carries the full burden for behavioral disclosure. The explicit '⚠️ Irreversible' warning highlights the permanent destructive nature, which is essential for a delete tool. However, it does not disclose behavior for invalid IDs or partial failures, which prevents a perfect score.

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 consists of two short sentences. The first is front-loaded with the action and resource, and the second adds a critical warning. Every word earns its place with no redundancy or filler.

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?

This is a low-complexity tool with a single parameter and no output schema. The description covers the main action and the critical irreversible nature. It does not address partial failure behavior or prerequisites, but given the simplicity and the inclusion of the most important safety warning, it is reasonably 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?

The schema already covers the single parameter 'ids' with a description 'Array of IDs', achieving 100% coverage. The description adds context that these are environment variable IDs, but this is already clear from the tool name and resource. No additional parameter semantics beyond the schema are provided, so 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 a specific action ('Delete') on a specific resource ('environment variables') with a qualifier ('by ids'). This distinguishes it from sibling tools like enable_envs, disable_envs, and update_env. The additional warning about irreversibility reinforces the 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 implies usage: when you need to permanently delete environment variables and have their IDs. The irreversibility warning provides caution but does not explicitly contrast with alternatives like disable_envs for temporary deactivation. No explicit 'use this when' or 'instead of' guidance is given.

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