Delete Folder

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

Beyond the destructiveHint annotation, the description warns that deletion is permanent, includes cascading deletion of contents, and cannot be undone via MCP. This adds significant behavioral context.

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 compact, logically structured (overview, args, returns, examples), and front-loaded with the key action. No unnecessary 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?

Given full schema coverage and annotations, the description provides examples, parameter interaction rules, and return type. For a destructive delete operation, it covers all necessary context.

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 coverage is 100%, so baseline is 3. The description adds priority rules (folderId takes precedence), explains the mutual requirement, and provides concrete examples, enhancing the schema descriptions.

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 ('Permanently delete') and resource ('folder from OmniFocus'), and clearly states the scope ('including any projects and folders it contains'). This distinguishes it from sibling tools like omnifocus_create_folder and omnifocus_update_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 explains how to provide the folder identifier (ID or name), that at least one is required, and that ID takes priority. It also notes permanence and irreversibility. While it doesn't explicitly contrast with omnifocus_delete_project or omnifocus_delete_task, the context is clear.

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