clasp_undeploy

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

With no annotations provided, the description carries the full burden. 'Remove a deployment' hints at destructiveness but doesn't disclose that the operation is likely irreversible, may require authentication, or how it handles missing identifiers. It also doesn't mention the 'all' flag's behavior, leaving side effects unclear.

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, efficient sentence with no filler. It's appropriately short for a simple operation, though it could include more detail without sacrificing conciseness.

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's complexity is moderate with two modes (specific deployment vs all), but the description omits the 'all' mode entirely and doesn't explain the behavior when no arguments are given. The schema helps, but the description alone is minimal, leaving the agent to infer crucial behavior.

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 covers all three parameters with descriptions, and the tool description adds nothing beyond that. Since schema description coverage is 100%, the baseline of 3 applies; the description does not enrich parameter understanding.

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 tool's function with a specific verb ('Remove') and resource ('a deployment'), directly matching the tool's name. While it doesn't explicitly contrast with sibling tools like clasp_deploy, the inverse relationship is evident, so it's clear but lacks explicit differentiation.

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. It doesn't mention that the 'all' flag removes all deployments or that a deploymentId is needed for a specific one, and it doesn't reference sibling tools like clasp_deployments or clasp_deploy.

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