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 an important limitation upfront ('Rejects mutations against published flows') and explains that edges define execution flow. But it omits other behavioral details such as persistence, side effects, validation behavior, or what happens when sourceHandle is missing.

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?

Three tight sentences with no filler. The core operation is first, the most important optional parameter semantics follow, and the usage triggers are front-loaded with a necessary restriction at the end. 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?

For a mutation tool with 7 parameters, no annotations, and no output schema, this description gives the essential purpose, a useful sourceHandle example, and a key restriction. It is functional but not fully complete: optional parameters are unexplained, return behavior is absent, and there is no mention of how to reverse or replace edges.

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 must compensate. It does add real meaning for sourceHandle with the concrete 'button-0' example and implies source/target semantics via 'connect two nodes'. However, data, type, targetHandle, and flowId are left undocumented, leaving significant parameter meaning to inference.

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 and resource: 'Connect two nodes in a flow with an edge.' It also clarifies what an edge is ('defines the flow execution path'), and the natural-language examples make the intended operation unmistakable. This clearly separates it from siblings like add_node, update_flow, and delete_edge.

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?

Provides explicit trigger phrasing: 'Use when the user says "connect the welcome message to the discount step" / "wire button 1 to the next node".' This is clear context for when the tool applies. However, it never states when not to use it or mentions alternatives such as update_flow or update_node for other connection-related changes.

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