delete_folder

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

No annotations are provided, so the description must carry the full burden. It only reveals that the folder must be empty; it does not disclose permanent deletion, error behavior on non-empty folders, or any output/confirmation. This is minimal for a destructive operation.

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 extremely concise—only four words—and has no filler. It is front-loaded and easy to parse, though the terseness borders on under-specification. Still, it wastes no 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?

This is a mutation tool with no annotations, no output schema, and only a one-line description. It does not explain what happens if the folder is non-empty, the irreversibility of the deletion, or any result/error behavior. The description is too incomplete for safe invocation.

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 input schema fully documents the single 'path' parameter with a clear description. Since schema coverage is 100%, the description adds little beyond the name and basic purpose, so the baseline score of 3 is appropriate.

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 ('delete') and resource ('folder'), and adds the important constraint 'empty'. It clearly distinguishes this tool from sibling tools like delete_note and aligns with create_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?

The description implies the tool is for deleting empty folders, which provides some usage context. However, it gives no explicit guidance on when to use this tool versus alternatives or what to do if the folder is not empty.

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