uninstall_environment

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

With no annotations provided, the description carries the full burden, and it discloses nothing about this destructive operation: no statement of irreversibility, data loss, required permissions, or confirmation requirements. 'Uninstall' is the only behavioral signal, and it comes from the name.

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 words is not conciseness but under-specification; there is nothing to front-load and no structure to evaluate. Brevity here reflects missing content rather than efficient writing.

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, two-required-parameter tool with no annotations, no output schema, and undocumented parameters, the definition leaves every question an agent would need answered unresolved.

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?

Two required parameters (id, type) have 0% schema description coverage, and the description supplies no meaning for either. The agent cannot tell whether 'type' is the environment kind, a stack identifier, or something else, nor how 'id' relates to it.

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 is effectively a restatement of the tool name: 'Uninstall environment' adds no verb detail, scope, or target beyond what the name already conveys. It does distinguish a destroy-style action from siblings like install_environment, but only by virtue of the name itself.

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?

There is no guidance on when to use this tool versus install_environment or list_environments, no stated prerequisites, and no indication of what conditions must hold before uninstalling. The agent receives no routing information at all.

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