Delete a team workspace

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

The description discloses that deletion is destructive, irreversible, and cascades to 'drops and members'. It also states the owner-only permission and credential requirement (ADR-0068). This significantly augments the destructiveHint annotation with specific consequences and prerequisites.

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 four crisp sentences that front-load the core purpose and then add necessary caveats (destructive, confirm, owner, credential) and a pointer for obtaining the workspace id. No filler.

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, two-parameter tool with an output schema, the description covers the action, consequences, permissions, confirmation requirement, and how to obtain required input. It leaves little ambiguity for an agent.

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 coverage is 100% with clear descriptions for both `workspace` and `confirm`. The description reiterates `confirm: true` and references dropthis_workspaces for the workspace id, but adds little beyond the schema for the parameters themselves.

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 'Permanently delete a team workspace by its id', specifying the verb (delete), resource (team workspace), and method (by id). This distinguishes it from sibling tools like dropthis_delete or workspace management tools.

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?

It provides explicit guidance: 'Owner only' establishes who may use it, 'requires `confirm: true`' is a prerequisite, and 'Use dropthis_workspaces to find the workspace id' points to a supporting tool. However, it doesn't explicitly contrast with other deletion tools, so slightly less than full alternative specification.

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