bp_connect_bp_pins

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

No annotations are provided, so the description carries the full behavioral burden. It discloses the registration precondition but says nothing about whether the connection is destructive/reversible, whether an existing wire on the destination pin is replaced, whether the graph must be recompiled, or what errors arise from type-mismatched pins.

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?

Lead sentence states the operation, followed by the precondition and a compact Args list. No filler, though the Args block largely restates the schema's parameter names.

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?

An output schema exists, so return values need not be explained. For a mutation tool with no annotations, the description covers the essential precondition but leaves error behavior, idempotency, and post-connect workflow (e.g., compiling) unaddressed.

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, and it documents all four parameters with roles: from_node/from_pin as the source/output side and to_node/to_pin as the destination/input side. This directional semantics is genuinely useful beyond the bare parameter names, though it omits expected ID/pin-name formats.

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 (connect) and resource (pins between registered Blueprint nodes), which is distinct from siblings like bp_set_bp_pin (single pin value) and bp_list_node_pins (read-only listing). An agent can identify exactly what this tool does without opening the schema.

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 an explicit precondition: both nodes must already be registered via bp_add_bp_node or bp_register_existing, and it names those two alternatives for the setup step. It does not state when-not to use this tool or what happens if the connection already exists, so it falls short of full routing guidance.

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