delete_workspace_action

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

The description explicitly states 'Permanently delete', which aligns with and reinforces the destructiveHint annotation. No contradictions exist, and the permanence is a useful behavioral detail beyond the generic annotation.

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 brief and to the point, with no unnecessary words. The workspace_id hint is front-loaded and useful, though the omission of action_id is a content issue rather than a conciseness issue.

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 is not complete for a two-parameter delete operation: it explains only one parameter and lacks any note about return value, side effects, or error conditions. The missing action_id explanation is a critical gap.

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?

Only workspace_id is described (as target workspace with a source). The required action_id parameter is completely undocumented, leaving a significant gap in parameter understanding.

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 tool's purpose: permanently delete a workspace automation action. This distinguishes it from other delete tools for different resource types (e.g., delete_hub_profile, delete_channel).

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?

Provides guidance for obtaining workspace_id via list_workspaces(), but omits any guidance for the required action_id parameter. It also does not specify when to use this tool versus alternatives, though the resource type is clear.

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