ue_bp_connect

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

No annotations are provided, so the description carries the burden. It discloses that the tool modifies the Blueprint and reports type mismatches with the involved types instead of failing silently. However, it does not mention side effects, return values, or error handling for other failures.

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 concise, with a clear purpose statement, a structured list of parameters, and a brief note about type incompatibility. Every part adds value, and it is not overly verbose.

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?

The tool has no output schema and no annotations, so the description should cover return behavior and common errors. It explains the type mismatch error but does not mention success output, prerequisites (e.g., node existence, blueprint compilability), or whether changes are saved. Given the moderate complexity, the description is adequate for the parameters but leaves some behavioral 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?

The description provides a detailed explanation for each of the six parameters, including examples for from_node and from_pin (event:ReceiveBeginPlay, 'then'). This adds substantial meaning beyond the bare string schema, covering the 0% schema coverage.

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 first sentence clearly states the action: connecting an output pin to an input pin of another node. It specifies the resource (Blueprint) and distinguishes from other Blueprint editing tools like adding nodes or events.

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 does not explicitly mention when to use this tool versus alternatives such as ue_bp_break_pin or adding nodes. Usage is implied by the function's purpose and the parameter list, but there is no guidance on prerequisites or when not to use it.

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