Delete a Node-RED flow (tab)

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the bar is lower, yet the description still adds significant value: the operation is irreversible ('cannot be undone from here'), it cascades to all nodes, and it requires HA_ALLOW_WRITE and HA_ALLOW_CONFIG_WRITE to be enabled. This prerequisite detail is not available anywhere in the structured fields.

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?

Three tight sentences, front-loaded with the action and scope, followed by the irreversibility warning and prerequisites. No filler, every clause earns its place.

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 mutation tool with no output schema, the description covers the critical unknowns an agent needs: scope of deletion, irreversibility, and the required environment flags. Combined with annotations and full schema coverage, nothing material is missing.

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 100%, so the baseline is 3. The description reinforces that the id targets a whole flow (tab) rather than a node, but adds no format or constraint detail beyond the schema, and says nothing about the optional instance_id parameter.

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 precise verb+resource ('Delete an entire Node-RED flow (one tab)') and clarifies scope: everything including all contained nodes, keyed by id. This clearly separates it from siblings like nodered_update_flow or nodered_set_flows.

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 (deleting a whole flow, not editing one) but never explicitly says when to prefer it over nodered_update_flow or nodered_set_flows, nor does it state that partial edits should use a different tool. Context is implied rather than spelled out.

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