set_skeletal_mesh_socket_parent

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

Annotations already declare this is a non-read-only, destructive, idempotent operation, so the safety profile is covered. The description adds useful behavioral context by stating that it validates the bone exists in the reference skeleton and by documenting the exact return fields, despite there being no output schema.

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 two compact sentences plus a return value line. It is front-loaded with the core action and contains no redundant or filler text.

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 full parameter documentation and annotations covering its safety profile, the description is complete enough to call correctly. It names the target resource, the precondition validation, and the return shape, leaving no major ambiguity.

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 100%, and all three parameters are documented in the schema with clear descriptions. The description adds only slight semantic context by tying the operation to a skeletal mesh and different bone, so the baseline 3 is appropriate.

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 and resource: re-parent an existing socket on a skeletal mesh to a different bone. This clearly distinguishes it from sibling socket tools like add_skeletal_mesh_socket, remove_skeletal_mesh_socket, rename_skeletal_mesh_socket, and set_skeletal_mesh_socket_transform.

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 implies the use case by specifying an existing socket and a different parent bone, so an agent can infer it is for re-parenting rather than creating or transforming a socket. However, 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.