set_parent

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 the behavioral nuance that omitting parent clears the relationship and that keep_transform preserves world transform. It does not fully explain the false case of keep_transform, but the primary behaviors are transparent.

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 extremely concise, using a single sentence to convey the core operation, the optional clearing behavior, and the transform option. It contains no unnecessary words and is well-structured.

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 simple parenting operation, the description covers the essential aspects: setting, clearing, and transform behavior. It does not mention return values or deeper scene side effects, but given the tool's simplicity, the provided information is sufficient for most usage contexts.

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 schema lists all three parameters with types and defaults; the description adds semantic meaning to parent (omission clears) and keep_transform (maintains world transform). The child parameter is self-explanatory in context, so overall the parameters are well-covered.

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 clearly states the tool sets a parent-child relationship and clarifies that omitting the parent clears it. It also specifies the keep_transform option, making the core purpose unambiguous and distinct from sibling parenting tools like parent_to_armature.

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 explains the basic action but does not explicitly indicate when to use this tool versus alternatives such as parent_to_armature or other parenting methods. The user may need domain knowledge to decide, so guidance is minimal.

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