delete_workspace

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

With no annotations provided, the description carries the behavioral burden. It adds useful context about permissions and the intended safe use case, but it does not disclose whether deletion is permanent, whether the workspace must be disabled first, or what consequences deleting a non-empty workspace would have.

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 sentence that front-loads the action and efficiently includes the permission requirement and safety condition. There is no wasted wording, and the key usage constraint is placed upfront.

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 tool with no annotations and no output schema, the description is thin on critical behavioral details like permanence, required prior workspace state, and what happens if the workspace is not empty. It mentions checking workspace status but does not say what status qualifies, leaving an agent to infer too much.

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 low (33%), and the description adds no parameter-level meaning. It does not explain what workspace_name should contain beyond its name, nor does it clarify the purpose of profile or the confirmation parameter, even though confirm_workspace_name is already documented in the schema.

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 identifies the action ('Delete') and the resource ('Survey Solutions workspace'), making the tool's purpose obvious. It does not explicitly differentiate from sibling workspace commands like disable_workspace or enable_workspace, but the deletion semantics are distinct enough that this is a minor gap.

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 gives explicit preconditions: requires admin_write permission and should only be used for empty/test workspaces after checking workspace status. It does not name alternative tools for workspaces that are not empty, but the 'only for empty/test' condition effectively defines when not to use it.

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