Delete an empty folder by providing its folder ID. Removes a folder from your Dynadot account only if it has no domains assigned to it.
Delete a folder. The folder must be empty (no domains assigned to it).
| Name | Required | Description | Default |
|---|---|---|---|
| folder_id | Yes | Folder ID to delete |
Changes observed during successful MCP inspections.
v1.3.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Discloses the emptiness precondition, a key behavioral constraint. No mention of permanence, auth, or side effects. Adequate but not rich.
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?
Two sentences, zero waste. Action and condition stated upfront.
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?
Simple tool with one parameter; description covers operation and constraint. No output schema needed. Well-suited to complexity.
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 covers folder_id with description; description adds precondition about emptiness, which is critical context beyond schema.
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?
Clear verb and resource: 'Delete a folder'. Specifies precondition (folder must be empty), distinguishing it from other folder actions like rename or list.
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?
Explicit precondition (must be empty) provides clear context; does not explicitly state when to use vs alternatives but enough for a destructive action.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.