delete_workspace_folder

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

With no annotations, the description carries the full burden and discloses key behaviors: default trash behavior and permanent deletion with flag. It could be improved by noting that trash behavior retains contents for potential restoration, but overall it is transparent.

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, front-loaded with the action, and contains no filler words. Every part contributes to understanding the tool's purpose and behavior.

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?

Given no output schema, the description does not mention return values or error conditions. Also lacks context on authorization or workspace ownership. For a simple delete tool, it is adequate but could be more complete by hinting at what happens after deletion (e.g., success response).

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%, so the description adds no extra parameter details beyond what the schema provides. The mention of 'permanent=true' in the description reinforces the parameter's purpose but does not add new semantic meaning.

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 folder from a workspace', specifying both the verb and resource. The workspace context differentiates it from sibling tools like 'delete_folder', which likely targets non-workspace folders.

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 default behavior (trash) and the optional permanent delete, providing context for usage. However, it does not explicitly guide when to use this tool over the similar 'delete_folder' or when not to use it (e.g., if restoration is needed).

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