delete_folder

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

With no annotations, the description carries the full burden of behavioral disclosure, but it only says a folder is deleted. It does not disclose whether deletion is permanent or reversible, whether non-empty folders are deleted recursively, or what effects occur beyond the folder itself.

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 definition is short and without filler, but this is under-specification rather than disciplined conciseness. A single sentence that merely restates the tool name does not earn high structure credit.

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 operation with no annotations, 0% schema coverage, and two parameters, the description is far from complete. An agent cannot determine what 'folder' and 'subpath' mean, whether deletion is permanent, or what safety checks are needed. The presence of an output schema does not compensate for these input and safety 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?

Schema description coverage is 0%, so the description must explain the parameters, but it does not. The word 'dossier' loosely maps to the required 'folder' parameter, while the optional 'subpath' parameter is completely unexplained and receives no semantic context.

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 'Supprime un dossier.' is a direct restatement of the tool name 'delete_folder' and adds no new information. It does identify the resource and action, but only by repeating what the name already communicates.

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 provides no guidance on when to use this tool versus alternatives such as delete_note, delete_asset, or trash_note. It does not mention prerequisites, exclusions, or any conditions that would make delete_folder the right choice.

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