delete_folder

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

The description discloses several behavioral traits: verification of folder existence and name matching, use of AppleScript, and detailed error messages. However, it does not specify whether deletion is permanent or moves to trash, what happens if the folder is not empty, or potential platform dependencies (AppleScript). With no annotations, this leaves gaps.

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 moderately concise but includes redundant bullet points (e.g., AppleScript verification mentioned twice). It could be more streamlined while retaining key information.

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?

The description states the output includes folder name, ID, deletion status, and method info, which is adequate for a simple mutation tool. However, missing details about edge cases (e.g., non-existent folder, non-empty folder) and platform constraints limit completeness.

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 description adds meaning beyond the input schema by explaining that folder_name is used for verification and folder_id for precise identification. This contextualizes both parameters beyond the schema's basic 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 clearly states the tool deletes a folder in Apple Notes by ID, using AppleScript verification. It specifies the verb 'delete' and the resource 'folder in Apple Notes', and distinguishes from siblings like rename_folder or move_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 usage for deleting a folder but does not provide explicit guidance on when to use this tool versus alternatives (e.g., delete_note). It lacks context on prerequisites or situations where deletion might be inappropriate, such as non-empty folders.

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