set_blueprint_parent_class

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

No annotations are provided, so the description carries the behavioral burden. It warns that this is a deliberate, impactful operation and instructs the agent to verify compatibility and recompile afterward, which is useful. However, it does not disclose whether the operation is reversible, what side effects may occur on existing graphs, or what errors might arise.

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 well-structured with a purpose statement, usage guidance, parameter explanations, a knowledge base pointer, and an example. Every section adds value and there is no filler or redundancy.

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 two-parameter mutation with an output schema, the description covers the main workflow, parameter semantics, and a concrete example. It could additionally mention failure modes or prerequisites, but the provided guidance plus KB reference is adequate for an agent to invoke it 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%, but the description adds an Args section explaining that blueprint_name is an asset name or path and that new_parent_class can be a Blueprint asset or C++ class name. The example further clarifies expected input format, which compensates well for the schema's missing descriptions.

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: 'Reparent an existing Blueprint to another Blueprint or C++ class.' This clearly identifies the operation and distinguishes it from sibling blueprint-editing tools like set_blueprint_property or set_blueprint_ai_controller.

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?

It explicitly says to use this for 'deliberate class-architecture changes' and gives a concrete workflow: inspect the Blueprint, confirm the new parent matches responsibilities, then compile and read back before further graph changes. It does not name alternatives, but the usage context is clear.

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