vibemk_delete_folder

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

With no annotations, the description must carry all behavioral detail. It mentions 'options for recursive deletion' but does not explain side effects, such as what happens with non-empty folders when abort_on_nonempty is selected, or whether deletion is permanent or requires activation.

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 direct, though it redundantly says 'Delete folder - Remove folder'. It is still concise and well-structured without unnecessary elaboration.

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 gives enough to understand the operation, but lacks important context such as whether the deletion affects child hosts, whether the action requires activation of changes, or how the delete_mode values behave in practice. It is not incomplete enough to be unusable, but leaves some gaps.

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 already provides full descriptions for both parameters (folder path and delete_mode). The tool description does not add any further semantic detail beyond what is in the schema, so it meets the baseline but does not exceed it.

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/remove folder) and mentions the key option for recursive deletion. It is easily distinguished from sibling tools such as create_folder, update_folder, and move_folder.

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?

No guidance is provided on when to use this tool versus alternatives, or how to decide between the delete modes. The description is purely declarative and does not offer any contextual or conditional advice.

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