sd_connect_nodes

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

Annotations provide no hints, so description carries burden. It mentions 'after direction, type, and duplicate checks,' indicating validation. However, it doesn't disclose whether the operation is destructive or how it affects the graph.

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?

Single sentence, concise, no redundant information. Front-loaded with the core action. Could be slightly more detailed without losing conciseness.

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?

With 5 required params, no schema descriptions, and an output schema not described, the description is insufficient. Does not explain graph ref structure, return value, or the nature of checks. Leaves significant gaps.

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%, but the description adds no explanation for any of the 5 parameters (graph, source_node, source_property, target_node, target_property). The names are self-explanatory but not elaborated.

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 indicates the tool connects runtime properties between nodes, with a specific verb and resource. It distinguishes from the sibling sd_disconnect_nodes by implying the opposite action, though not explicitly.

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 guidance on when to use this tool versus alternatives like sd_disconnect_nodes or other graph manipulation tools. No when-not or context provided.

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