add_sequence_node

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

With no annotations, the description carries the full burden and does a good job: it explains the Sequence node's execution order, output pin naming, the number of outputs range, and optional positioning. It does not mention subschema return details or possible side effects beyond the obvious 'add node' mutation, but the provided behavioral semantics are clear and accurate.

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 well-structured: a brief purpose statement, a one-line behavioral explanation, a concise Args block, a KB pointer, and a concrete example. Every part earns its place without redundant filler.

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 relatively simple three-parameter tool, the description is nearly complete: it covers purpose, parameter semantics, and an example. An output schema exists, so return values need not be described. A small gap is that it does not specify which graph or context the node is added to, which could matter in blueprint editing, but overall the agent has enough information to invoke the tool 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 0%, so the description is the only source of parameter meaning. It provides meaningful definitions for all three parameters: blueprint_name, num_outputs with the 2-10 range, and node_position as an optional [X, Y] graph position. This fully compensates for the bare 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 that the tool adds a Sequence node and explains what that means ('executes outputs in order'). It identifies the specific resource and behavior, which is distinct from many other add-node tools in the sibling list. However, it does not explicitly differentiate from the similarly named `add_blueprint_sequence_node`, so it misses the highest bar for sibling differentiation.

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 says the node is 'useful for organizing multiple sequential actions,' which gives clear contextual guidance on when to use it. It does not explicitly mention alternatives or when not to use it, but the use-case statement is enough to guide an agent toward this tool for sequential execution flow.

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