Replace ALL Node-RED flows

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

Annotations already flag destructiveHint=true, and the description compounds that with concrete detail: the whole config is overwritten, existing tabs are destroyed, optimistic concurrency via rev, and the two environment flags (HA_ALLOW_WRITE, HA_ALLOW_CONFIG_WRITE) required for the call to succeed.

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?

Front-loads the destructive scope in the first sentence, then routes to alternatives, then adds the concurrency and deployment semantics. Every clause carries operational information; nothing is filler.

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 with no output schema, the description covers scope, alternatives, concurrency, deploy modes, and required auth flags. Nothing an agent needs in order to call it safely 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 coverage is already 100%, so the schema documents all four parameters. The description still adds genuine meaning beyond it by explaining what each deployment_type value does to running flows (full restarts all; flows/nodes restart only what changed; reload re-reads from storage), which the enum alone does not convey.

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 specific verb and resource ('Replace the ENTIRE Node-RED flow configuration and deploy') and explicitly scopes it as whole-config replacement. It names the sibling tools it should not be confused with (nodered_create_flow / nodered_update_flow), so an agent can distinguish it without opening another schema.

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?

Gives an explicit when-not-to-use rule ('prefer nodered_create_flow / nodered_update_flow unless you really mean to rewrite everything') and a concrete precondition for safe use ('Pass the rev from nodered_get_flows to avoid clobbering a concurrent change'). Alternatives and conditions are both named.

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