Create a directed dependency edge between a source and target node in a PipelineFlow pipeline, defining upstream-to-downstream execution order.
Establish directed dependency edge from source node to target node.
| Name | Required | Description | Default |
|---|---|---|---|
| to_node | Yes | Target downstream node. | |
| from_node | Yes | Source upstream node. | |
| pipeline_id | Yes | Target pipeline ID. |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of behavioral disclosure. It implies a mutation by saying 'establish,' but does not state permissions, reversibility, duplicate-edge handling, cycle constraints, or impact on pipeline execution.
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 a single, front-loaded sentence with no wasted words. It communicates the core operation efficiently and is appropriately sized for a simple edge-creation tool.
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 mutation tool with no annotations and no output schema, the description is incomplete. It states the basic operation but omits prerequisites, safety traits, and error conditions, leaving the agent without important behavioral context.
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 the schema already documents all three parameters. The description mentions source and target nodes but adds no format, constraint, or syntax details beyond what the schema provides, making the baseline score of 3 appropriate.
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 states a specific verb and resource: establish a directed dependency edge from source node to target node. This clearly distinguishes the tool from sibling pipeline and node management tools, though it does not explicitly name or contrast any sibling.
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 provides no explicit when-to-use guidance, prerequisites, or alternatives. It implies the tool is for creating dependency edges, but does not say when to call it, whether nodes must already exist, or how it relates to sibling tools like add_node.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.