delete_env_var

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

With no annotations provided, the description carries the full burden. It discloses that it reads current state before writing ('Lê estado atual antes de escrever') and requires confirmation, which adds behavioral context beyond the schema. However, it doesn't describe what happens if the variable doesn't exist or other edge cases.

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 very concise (two short sentences) with a warning symbol at the start. Every sentence adds value with no wasted words.

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?

The description does not explain the return value or result (e.g., success/failure messages) and does not explicitly state what entity the variable is removed from (project/service), though the parameters clarify it. Given no output schema, some additional context would be helpful.

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%, and the description adds minimal parameter information beyond repeating the confirmation value ('CONFIRMO'). Baseline of 3 is appropriate since the schema already documents each parameter.

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 it removes one environment variable ('Remove UMA variável de ambiente'), using a specific verb and resource. It implicitly distinguishes from sibling tools like set_env_var and get_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 provides usage-related information such as the required confirmation ('Requer confirm: "CONFIRMO"') and a safety precaution, but it does not explicitly state when to use this tool versus alternative tools like set_env_var or when not to use it.

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