datalens_cloudenvironments_deleteDeletes a DataLens cloud environment and returns the deletion operation.
Delete a cloud environment and return the operation that deletes it.
Experimental in the DataLens API, written from its document and never called: not measured.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Id of the cloud environment. |
Changes observed during successful MCP inspections.
v0.122.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare destructiveHint=true, idempotentHint=false, and openWorldHint=true. The description adds a useful experimental/never-called caveat but does not explain what gets destroyed, whether deletion is reversible, or required permissions—leaving key behavioral context to the annotations.
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?
Two sentences, front-loaded with the core purpose, followed by a relevant experimental caveat. 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?
For a destructive delete operation whose safety profile is covered by annotations, the description is minimally adequate but lacks any prerequisites, consequences, or usage context that would help an agent invoke it correctly.
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% for the single 'id' parameter. The description adds no additional meaning or syntax beyond what the schema already provides, so the baseline of 3 applies.
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?
States the specific verb 'Delete' and resource 'cloud environment', clearly distinguishing it from siblings like datalens_cloudenvironments_list/get/create/update. It also clarifies the return type as an operation.
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?
Provides no guidance on when to use this tool versus alternatives, nor any prerequisites or warnings. The experimental note is a caveat about reliability, not usage guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.