nodered_deploy_flows

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

With no annotations, the description carries the full burden. It does disclose the most important behavior for a mutation tool: this replaces the *running* document (destructive/overwriting) and demands an explicit confirm flag as a guard. It stops short of saying whether the prior flow set is recoverable, whether the deploy is atomic/validated, or what happens on partial failure.

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 short sentences, front-loaded with the action and the safety requirement. Nothing is padded, though the terseness shades into under-specification rather than pure economy.

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?

An output schema exists, so return values need not be described. What an agent still needs before calling correctly — the expected format/content of flows_json and the blast radius of replacing the running document — is absent, so the definition is only minimally complete for a whole-document mutation.

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 0% and there are two parameters. The description explains confirm's purpose (a required confirmation gate), covering one of the two. flows_json — the entire document payload and required argument — gets no format, size, or shape guidance anywhere, so the description only partially compensates for the coverage gap.

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 concrete verb+resource: 'POST /flows and replace the running Node-RED document,' making clear this deploys a whole flow document. It implicitly contrasts with nodered_add_flow by saying it *replaces* rather than adds, but it never names that sibling or scopes the operation explicitly, so differentiation is left to inference.

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?

Provides one concrete prerequisite ('confirm=true required'), which is real usage guidance. However it gives no when-to-use framing versus nodered_add_flow or marketplace_deploy, and no conditions under which this should be avoided. Adequate but with clear gaps.

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