nodered_add_flow

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

With no annotations, the description carries the full burden. It usefully discloses two behavioral facts: the operation mutates by appending (not replacing) and that it triggers a redeploy, plus the confirm gate. It says nothing about permissions, reversibility, what happens to existing nodes on conflict, or failure behavior.

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 tight sentences with the action front-loaded and the prerequisite immediately after. No filler, though the second sentence is terse to the point of being a fragment.

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. For a mutating tool with zero annotations, the definition covers the safety gate but omits the flow_json payload format and any side-effect detail, leaving meaningful gaps.

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 0%, so the description must compensate. It correctly flags that confirm must be true, which is critical because the schema defaults it to false and does not list it as required. However, flow_json — the required parameter — gets no format or content explanation at all.

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 gives a concrete verb and resource: append nodes to current flows and redeploy. That distinguishes it from nodered_list_flows and nodered_deploy_flows, though it never names those siblings explicitly, so the differentiation is inferable rather than stated.

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?

It states a hard prerequisite (confirm=true required) but gives no guidance on when to choose this over nodered_deploy_flows, nodered_install_node, or nodered_inject. Usage context is implied by the name rather than explained.

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