connect_anim_graph_nodes

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

No annotations are present, so the description carries the behavioral burden. It adds useful workflow awareness by mentioning compatibility, prior node-ID inspection, and post-connect compile diagnostics/readback. However, it does not disclose failure modes, whether existing connections are replaced, or what happens on incompatible 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?

The description is front-loaded with the core action, then gives workflow order, parameter meanings, a KB reference, and an example. Every section earns its place without redundant filler.

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?

Given that an output schema exists, return values do not need to be described. The description covers prerequisites, parameter semantics, workflow follow-up, and a KB pointer. It is slightly thin on pin-compatibility semantics and explicit alternatives, but is adequate for correct invocation.

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 input schema has 0% description coverage, so the description compensates by explaining each parameter: asset path/name, source and target GUIDs, and the optional graph_name with its default. The example further clarifies real invocation shape.

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 opens with a specific verb and resource: 'Connect compatible pose pins between two AnimGraph nodes.' It clearly scopes the tool to AnimGraph nodes and pose pins, distinguishing it from generic node-connection tools like connect_blueprint_nodes or bp_connect_pins.

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 gives explicit workflow context: 'Use this after inspecting AnimGraph node IDs' and 'Follow with AnimBP compile diagnostics and readback.' This is clear context, but it does not explicitly name alternatives or state when not to use this tool.

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