delete_service_env

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

The description adds that deletion is permanent ('permanently removes'), which is critical behavioral information beyond the tool name. However, with no annotations provided, it omits other important traits like required permissions or impact on running services, leaving gaps.

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 extremely concise, consisting of two short sentences that immediately convey the action. There is no fluff or unnecessary information, making it easy to parse quickly.

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?

For a simple delete tool, the description adequately explains the outcome (permanent removal). However, it could be more complete by referencing list_service_envs to obtain the env_uuid, which is mentioned only in the schema. The lack of output schema reduces the need for return value explanation.

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 input schema has 100% coverage with descriptions for both parameters (env_uuid, service_uuid). The description itself adds no additional parameter meaning beyond what the schema already provides, so the baseline score of 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 the action: 'Delete an environment variable from a service.' It uses a specific verb and resource, making the purpose obvious. However, it does not explicitly differentiate from sibling tools like delete_application_env, but the context of service vs application is implicit.

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 no guidance on when to use this tool versus alternatives (e.g., update_service_env, delete_application_env). It does not mention prerequisites, such as needing to list env vars first, nor does it state 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.