delete_env

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

Description adds key behavioral details beyond annotations: mentions idempotency, skipped keys (no error), and that it takes effect on next deploy. Annotations already mark destructiveHint and idempotentHint; description enriches with 'skipped' behavior.

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?

Three sentences, each serving a distinct purpose: operation description, usage modes, behavioral nuance. No fluff.

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?

Coverage is high given annotations and schema. The description clarifies the behavior for missing keys and the effect timing. Minor gap: could mention if the tool requires specific permissions.

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 coverage is 100% so parameters are documented. Description adds meaning by explaining the relationship between `key` and `keys`, and the side-effect of 'skipped'. Could mention that `key` and `keys` are mutually exclusive.

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), resource (environment variables), and specifies the two modes (single via `key`, batch via `keys`). It distinguishes from sibling tools like `set_env` and `list_env`.

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?

Explicitly explains that missing keys are reported in `skipped` without error, making the tool idempotent. Does not explicitly mention when not to use, but the context is clear for a delete operation.

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