websex_workspace_delete

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It hints that non-empty directories are not deletable, but says nothing about irreversibility, whether deletion prompts for confirmation, required permissions, or error behavior on a missing path — significant gaps for a destructive 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?

A single front-loaded sentence with no filler; the verb and scope appear immediately. Nothing in it is redundant.

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?

An output schema exists so return values need no explanation, but for a destructive tool with zero annotations and 0% parameter coverage, the description should disclose irreversibility, directory semantics, and parameter formats. It does not, so it is incomplete for the operation's risk level.

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 0% and both parameters (path, engagement_id) lack any documentation. The phrase 'inside the WebSex engagement workspace' loosely implies path is workspace-relative, but the description does not specify path format (absolute vs relative, separators) or what engagement_id scopes, leaving both parameters under-explained.

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 names a specific verb (delete) and resource (one file or empty directory inside the workspace), which cleanly separates it from websex_workspace_read, websex_workspace_write, and websex_workspace_list. The 'one file or empty directory' scope qualifier is a useful precision point, but no sibling tool is named for contrast.

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 versus deleting via websex_bash or websex_execute, nor on prerequisites such as needing a valid engagement_id. The only implicit usage hint is the 'empty directory' restriction, which is a constraint rather than when-to-use guidance.

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