delete_workspace

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

No annotations are provided, so the description bears the full burden of disclosing behavioral traits. It states the destructive action ('Delete') but does not explain irreversible consequences, cascading deletion of associated projects/files, authentication requirements, or any confirmation/rollback behavior. For a destructive operation, this is a significant transparency gap.

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, front-loaded sentence that communicates the core action and ownership condition without any fluff. It is concise and wastes no words, though it may be too terse given the missing behavioral and parameter detail.

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?

Given that this is a destructive operation with no annotations or output schema, the description should explain consequences, ownership verification, and what happens to associated data. It only mentions ownership, leaving the agent without critical safety and context information. It is incomplete for reliable use.

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%, meaning the schema provides no documentation for workspace_id. The description also adds no explanation of what workspace_id is, how to obtain it, or its format. The agent must infer everything from the parameter name alone, which is insufficient for correct invocation.

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 (remove)') and the resource ('a workspace'), and adds the ownership qualifier 'you own', which differentiates it from operations on other resources. It is unambiguous and distinct from siblings like list_workspaces or get_workspace.

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 phrase 'a workspace you own' implies a condition for use, but the description does not explicitly state when to use this tool versus alternatives, nor does it mention exclusions (e.g., 'do not use for workspaces shared with you') or prerequisites like verifying ownership. The guidance is implicit rather than explicit.

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