directus_delete_folder

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It correctly notes the operation is irreversible, but fails to disclose critical mutation details such as whether deletion cascades to child items/folders, if the action is synchronous, or required permissions.

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 two-sentence structure is appropriately brief, though the '[UNIFIED]' prefix appears to be metadata noise that does not aid comprehension. The content is front-loaded but inadequate given the complete lack of parameter documentation in the schema.

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 zero schema coverage and no output schema, the description is insufficient. It omits expected details for folder deletion: content disposition (what happens to items inside), parameter explanations, error conditions, and return value structure.

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% for both required parameters (`site` and `id`). The description provides no compensatory semantic information—failing to explain what `site` refers to or that `id` is the folder identifier—leaving parameters completely undocumented.

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?

States a specific verb (Delete) and resource (folder). However, it does not clarify that this is a Directus-specific folder operation or distinguish from sibling tools like `directus_delete_file` or `directus_delete_collection`, relying solely on the tool name for 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?

Provides only a destructiveness warning ('irreversible') but lacks any guidance on when to use this versus alternatives (e.g., `directus_delete_files` for contents), prerequisites (e.g., whether the folder must be empty), or workflow integration.

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