remove_deployment

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

With no annotations, the description carries the full burden of behavioral disclosure. It only states 'Remove/cancel' without explaining whether the operation is permanent, reversible, or what happens to associated resources, leaving significant ambiguity about side effects.

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?

A single short sentence with no filler, effectively front-loaded and appropriately sized for a simple tool. The wording is direct and unambiguous in its core intent.

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?

The tool is a destructive operation (remove/cancel) yet lacks any context about permanence, reversibility, or prerequisites, and fails to clarify the apparent synonymy of 'remove' and 'cancel' or when each applies. More detail is expected for a mutation tool.

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 already fully describes the sole parameter (deploymentId) with the description 'The deployment ID to remove', so the tool description adds no additional semantic value. Baseline 3 is appropriate given 100% schema coverage.

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 ('Remove/cancel') and target resource ('a specific deployment'), making it distinct from related tools like restart_deployment or redeploy_service.

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?

No guidance is provided on when to use this tool versus alternatives such as restart_deployment or get_deployment, nor any prerequisites (e.g., whether the deployment must be inactive). The description only implies usage for removing a deployment.

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