sigma_delete_workspace

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

Annotations already indicate destructiveHint=true and readOnlyHint=false. The description adds valuable behavioral context by stating that confirm=True is required, which is not apparent from the schema (confirm defaults to false). It does not contradict annotations, but does not describe long-term consequences or associated resource effects.

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 minimal and front-loaded: 'Delete a workspace. Requires confirm=True.' Every sentence earns its place with no unnecessary words.

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 delete operation, the description covers the essential requirement (confirm=True) and the resource being deleted. The output schema exists and annotations indicate destructive intent, reducing the need to explain return values. It omits details about irreversible consequences, but the simplicity of the tool and annotations make it reasonably complete.

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%, so the description must compensate. It adds meaning to 'confirm' by explaining it must be true, which is critical. However, 'workspace_id' is not elaborated beyond its name, leaving the user to infer its source or format.

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 uses a specific verb and resource ('Delete a workspace'), clearly distinguishing it from sibling tools like sigma_delete_team and sigma_delete_file. It is direct and unambiguous.

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 mentions 'Requires confirm=True', which is a prerequisite for use, but gives no explicit guidance on when to use this tool versus alternatives or when not to use it. Sibling context suggests delete operations are distinct, but no alternative tools are referenced.

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