n8n_scaffold_browser_bridge_node

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

No annotations are provided, so the description carries full burden. It discloses that the tool generates JSON locally without calling the n8n API, and describes two modes. It does not explicitly state how the output is delivered (e.g., stdout), but 'ready-to-paste' implies the JSON is output. The description is consistent and clear.

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?

The description is concise with three sentences: one for main purpose, one for context, and one for mode details. It is front-loaded with the primary action and contains no filler. Every sentence earns its place.

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?

Given the tool's complexity (7 parameters, nested objects, enum), the schema provides full parameter coverage. The description adds context about the local generation and modes. It could mention the output format more explicitly, but overall it is complete enough for an agent to use correctly.

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 100%, so a baseline of 3 is appropriate. The description adds value by explaining the two modes and the default behavior, but most parameter semantics are already covered in the input schema. Little extra meaning beyond the schema.

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 clearly states the tool generates a ready-to-paste n8n node JSON for a given platform, action, and input. It specifies the resource (n8n node for browser-bridge) and verb (generate), and distinguishes from sibling tools (which are other n8n utilities not related to scaffolding).

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?

The description implies when to use this tool: when you need to create an n8n node for browser-bridge without rediscovering the spawn/heredoc pattern. It also explains there are two modes ('code-node' and 'execute-command') with default indicated. However, it doesn't explicitly state when NOT to use it or name alternative tools, though none of the siblings are relevant.

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