nodered_inject

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

With no annotations, the description carries the full behavioral burden and drops it. 'Trigger' implies an action with side effects, but nothing states whether it requires the flow to be deployed, whether it mutates anything persistent, whether it's idempotent, or what the caller gets back. There is no auth, rate-limit, or reversibility context.

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 sentence with no filler. It is not padded, though 'by id' is the only structural content and a clause on effect would have fit.

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 explained, and a single required param keeps the interface small. Still, for an action-bearing tool with no annotations, the description leaves foundational facts (deployment prerequisite, side effects) entirely unstated, so it is only minimally complete.

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?

Only one parameter, and the schema documents it by title only (0% description coverage). The description at least ties node_id to the inject-node concept, so it adds marginal meaning over the bare schema, but gives no format (e.g., how a Node-RED node id looks) or constraint. Baseline 3 for a single param the description doesn't clarify further.

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 (Trigger) and resource (inject node) plus the keying parameter, which is enough to distinguish it from the other nodered_* siblings (info, list_flows, deploy_flows, add_flow, install_node). It loses a point only because it never says what an 'inject node' does — that triggering it injects a message into a flow — which an agent needs to reason about effects.

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?

No when-to-use guidance at all. Nothing tells the agent whether this is the right tool for injecting a message versus deploying flows or adding nodes, nor that the node must already exist in a deployed flow. Pure one-line capability statement.

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