Deletes the specified proxy folder.

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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the safety profile is covered structurally. The description adds that the folder must exist within the specified workspace, but it does not explain what happens to folder contents, permissions, or failure behavior for non-empty folders.

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 short sentences and front-loads the deletion action. It is efficient overall, though "This method" is mild filler and the second sentence could more directly state the prerequisite.

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 folder-deletion tool, the description covers the basic action and the existence prerequisite, and annotations carry the destructive/idempotent safety context. However, it omits the critical distinction from delete_proxy_folder_with_contents and does not clarify whether a non-empty folder will be rejected or what happens to contents.

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 100%, so the schema already documents both workspaceId and proxyFolderId. The description reinforces that proxyFolderId must reference an existing folder within the workspace, but adds little parameter detail beyond that.

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 states a specific verb and resource: it deletes a proxy folder. It does not distinguish this tool from the sibling delete_proxy_folder_with_contents, which is an important nearby alternative, so it stops short of a 5.

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 gives a prerequisite that proxyFolderId must match an existing folder in the workspace, but it does not say when to use this tool rather than delete_proxy_folder_with_contents or other deletion tools. The usage is only implied by the tool name and operation.

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