delete_folder

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

No annotations are provided, so the description must disclose behavior. It only states the empty-folder requirement, but does not mention that deletion is permanent, whether it fails on non-empty folders, or any permission requirements. This is minimal disclosure 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 short, with one sentence and an args block. Every word earns its place, and it is front-loaded with the action. No redundant content.

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 simple single-parameter delete tool, the description is somewhat adequate but lacks context about error behavior or permanence. It does mention the critical empty-folder requirement, which is useful. The output schema exists but the description doesn't need to explain return values. However, given the tool's destructive nature, more context would help.

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 has a single 'name' string with no description. The description adds 'Namn på mappen att ta bort' (name of the folder to delete), giving semantic meaning to the parameter. However, it is essentially a restatement of the parameter's purpose and adds no format or validation details.

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: 'Ta bort en mapp' (delete a folder). It also adds a constraining condition ('måste vara tom' – must be empty), which distinguishes this tool from rename_folder or create_folder. The verb and resource are specific.

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 provides a clear precondition that the folder must be empty before deletion. However, it does not mention when to use this instead of delete_email or rename_folder, nor does it specify any exclusion scenarios beyond emptiness.

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