Delete folder

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

The annotation `destructiveHint: true` already signals destructive behavior, but the description adds no further context. It does not disclose whether the deletion is reversible, whether it affects subfolders, or any permission requirements. Given the sibling 'permanently_delete', this ambiguity is significant.

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 a single, concise sentence that is easy to parse and front-loads the primary action. While minimal, it is not wordy and effectively communicates the core purpose.

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?

With only one parameter and no output schema, the description still leaves critical gaps. It does not explain the deletion behavior (soft vs. permanent), recovery options, or how it relates to sibling tools like 'restore_from_trash' and 'permanently_delete'. This is insufficient for a 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 100% (the only parameter `folder_uuid` is described as 'Folder UUID'), so the schema already provides full parameter semantics. The description adds no additional meaning beyond that baseline.

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 'Delete a folder' clearly states the action and resource. However, it does not distinguish this from the sibling 'permanently_delete', which may be a more permanent deletion method. Thus it lacks clear differentiation.

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?

There is no guidance on when to use this tool versus alternatives like 'permanently_delete' or 'restore_from_trash'. The description does not mention whether the folder is moved to trash, nor any prerequisites or consequences.

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