Delete env var

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

With no annotations, the description must convey behavioral traits. It only states the deletion action, with no mention of permanence, side effects, error behavior, or required permissions. This leaves significant ambiguity for a destructive operation.

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, front-loaded sentence with no redundant or extraneous information. It is appropriately concise for a straightforward delete operation.

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 no annotations and no output schema, the description leaves gaps: the role of 'uuid' is unclear, and delete behavior (e.g., irreversibility, impact on running apps) is not disclosed. The description is insufficient for fully understanding the tool's semantics.

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 has two required parameters (uuid and env_uuid) with no descriptions. The description only clarifies 'env UUID' for env_uuid, leaving the purpose of 'uuid' ambiguous. With 0% schema coverage, the description should explain both parameters.

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 action ('Delete'), the resource ('environment variable'), and the scope ('from an application by env UUID'). This precisely distinguishes it from sibling tools like createEnv and updateEnv.

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 usage context is implied: to delete an environment variable, use this tool. However, it does not explicitly state when to prefer this over alternatives (e.g., updateEnv) or mention conditions/exclusions.

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