Delete Workspace

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

With no annotations, the description carries the full burden. It only states 'permanently', implying irreversibility, but fails to disclose other important behaviors like cascading deletion of contents, permission requirements, or failure conditions. This is insufficient for a delete operation.

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 at one sentence, front-loading the key action. However, it may be too sparse, omitting critical details like irreversibility emphasis. Nevertheless, every word earns its place.

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 operation with one parameter and no output schema, the description provides the core purpose but lacks essential context such as irreversible consequences, required permissions, or side effects. Completeness is inadequate for safe tool usage.

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 already provides 100% coverage with a single parameter described as 'Workspace ID'. The description adds no further semantic meaning beyond what the schema offers, so a 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) and the resource (workspace), and the adverb 'permanently' distinguishes it from non-destructive operations like update_workspace. Among sibling tools, it is uniquely identifiable.

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 prerequisites, such as requiring the workspace to be empty or the user to be an owner. No exclusion criteria or alternative tools are mentioned. For a destructive operation, explicit 'when to use' and 'when not to use' would be valuable.

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