Remove a node and its sub-items from WorkFlowy outlines to manage hierarchical task lists and maintain organized workflows.
Delete a WorkFlowy node and all its children
| Name | Required | Description | Default |
|---|---|---|---|
| node_id | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
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 states the tool deletes a node and its children, implying a destructive mutation, but lacks details on permissions needed, irreversibility, error conditions, or rate limits, leaving significant gaps for a deletion operation.
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 a single, efficient sentence that front-loads the core action ('Delete') and resource, with zero wasted words. It's appropriately sized for a simple tool with one parameter.
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 the tool's destructive nature and lack of annotations, the description is minimally adequate but incomplete. It specifies what the tool does but omits critical behavioral context (e.g., permanence, errors). The presence of an output schema helps, but more guidance is needed for safe use.
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 doesn't add specific details about the 'node_id' parameter beyond what the schema implies (a string identifier). However, with only one parameter and 0% schema description coverage, the description's clarity about the tool's purpose provides adequate context, compensating for the minimal parameter documentation.
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 specific action ('Delete') and resource ('a WorkFlowy node and all its children'), distinguishing it from siblings like workflowy_update_node or workflowy_get_node by focusing on permanent removal rather than modification or retrieval.
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?
No explicit guidance is provided on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., node must exist), exclusions (e.g., cannot delete root nodes), or compare to siblings like workflowy_uncomplete_node for different deletion scenarios.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.