set_component_parent_socket

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

With no annotations, the description carries the behavioral burden, and it does so well: it explains that UE5 positions the component automatically following skeleton animation, and it discloses that omitting parent_component only updates the socket name on the current parent. It does not cover edge cases or prerequisites, but the core behavioral traits are clearly stated.

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 longer than average, but each section earns its place: purpose, context, common socket names, argument explanations, return format, KB reference, and example. The socket-name list is somewhat extensive but directly useful for selecting a valid parent_socket value.

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 no annotations, the description provides the essential invocation details, parameter meanings, common values, optional-parameter behavior, return shape, and an example. It could be more complete by describing error conditions or prerequisites, but the agent has enough guidance to select and call the tool correctly.

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%, and the description fully compensates by explaining every parameter: blueprint_name, component_name, parent_socket, and the optional parent_component with its omission behavior. It also provides concrete example values, including a list of common UE5 Mannequin socket names, which adds significant practical meaning beyond the bare schema.

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: 'Attach a Blueprint component to a named bone/socket on its parent SkeletalMeshComponent.' It clearly identifies what the tool does and its intended use for attaching armor pieces to skeleton sockets. It does not name or explicitly contrast a sibling tool, but the behavior is distinctive enough that an agent can infer when it applies.

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 clear usage context: it is 'the correct way to make armor pieces snap to the right place,' and it contrasts with manually tweaking relative transforms. This tells an agent when the tool is appropriate. It does not explicitly list exclusions or alternative tool names, but the context is strong.

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