Workspace Delete Workspace

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is covered. The description adds a valuable behavioral detail—that confirm=True is required—which is not present in the annotations. It does not describe cascading effects or irreversibility, but with annotations carrying the destructive warning, this is a useful addition.

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?

Two short sentences, front-loaded with the core action and immediately followed by the required condition. No filler or redundancy.

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 operation with an output schema and annotations covering safety, the description is minimally adequate. It mentions the confirm requirement but omits consequences of deletion (e.g., what happens to files, grants, or members) and required permissions, leaving meaningful gaps for a high-stakes operation.

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% for both parameters. The description clarifies that confirm must be True, which adds meaning beyond the schema's default of false. However, workspace_id is not explained at all (format, source), so the description compensates for only one of two undocumented parameters.

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?

States a specific verb ('Delete') and resource ('workspace'), making the operation unambiguous. It does not explicitly contrast with sibling workspace tools, but the name and description are clear enough to distinguish it from list/get/create variants.

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 states a prerequisite ('Requires confirm=True') but gives no guidance on when to use this destructive operation versus alternatives like deactivating or archiving a workspace. Usage is implied by the tool name, but explicit when/when-not guidance is absent.

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