nodered_info

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

With no annotations, the description carries the full behavioral burden. It does disclose a meaningful trait beyond the schema: the data comes from the loopback Admin API, which tells the agent this hits a locally running Node-RED instance. It does not state that the call is read-only, nor any auth or failure behavior, so a 3 is appropriate.

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?

One short, front-loaded fragment with no filler; the resource list leads and the data source trails. It is a noun phrase rather than a verb-led sentence, which slightly weakens immediacy but costs nothing in length.

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 zero-parameter info tool with an output schema already defining the return shape, the description supplies adequate scope (settings, diagnostics, palette). It omits only the read-only assurance and any precondition that Node-RED be reachable, which are minor for a diagnostic read.

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 tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline for a no-arg tool is 4.

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 names a specific resource (Node-RED settings, diagnostics, and palette) and the source it reads from (the loopback Admin API), which is enough to distinguish it from siblings like nodered_list_flows or nodered_inject. It never explicitly contrasts itself with those siblings, so it stops short of a 5.

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?

Usage is only implied: an agent can infer this is the tool for inspecting Node-RED configuration and health, but the description gives no when-to-use condition, no prerequisites (e.g. Node-RED must be running), and names no alternative.

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