gtm_delete_workspace

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

No annotations are provided, so the description carries the full burden. It discloses irreversibility ('This cannot be undone') and suggests a pre-check, which covers the main safety concern. However, it does not mention the required 'confirm' flag or any permissions needed, which are relevant behavioral aspects.

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 two sentences with zero waste. It front-loads the destructive consequence and then gives a critical pre-step. Every sentence earns its place and is well-structured for quick reading.

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?

The description gives essential safety context (irreversibility and checking status) but omits parameter semantics and does not clarify the confirm flag, which is a critical piece for executing a destructive operation. While an output schema exists, the lack of parameter guidance makes it incomplete for a 4-param destructive tool.

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?

The schema description coverage is 0%, so the description must explain parameters. It provides no information about workspace_id, confirm, account_id, or container_id. It only vaguely refers to a 'workspace' without linking to the parameters, leaving the agent without guidance on how to fill them correctly.

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 a workspace) and the resource, and explicitly notes that it discards uncommitted changes. This distinguishes it from sibling tools like gtm_sync_workspace or gtm_create_workspace by emphasizing the destructive nature, leaving no ambiguity about what the tool does.

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 explicitly tells when to use the tool (to delete a workspace and discard changes) and advises running workspace_status first to see what will be thrown away. This is a clear usage guideline with a precaution, effectively guiding agent behavior before invocation.

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