generate_blueprint_compatible_class

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states the generation outcome without mentioning side effects like file creation, project modification, or code insertion. The mutation of the project is implied but not detailed.

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 a single, crisp sentence that front-loads the purpose without filler. Every word contributes to understanding the core function, making it highly concise and 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?

Given the tool's complexity (5 parameters, nested arrays for functions/properties, no output schema or annotations), the description is too sparse. It omits details about code generation behavior, default values, parent class handling, and potential side effects, leaving the agent without enough context to predict outcomes.

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 already describes all 5 parameters with 100% coverage, so the baseline is 3. The description adds minimal value by referencing properties and functions exposed to Blueprints, but it does not clarify parameter formats, types, or relationships beyond what the schema provides.

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 generates a Blueprint-compatible C++ class, naming the resource and the specific features (properties and functions exposed to Blueprints). This distinguishes it from sibling generators like generate_uclass or generate_actor_component by emphasizing Blueprint compatibility.

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?

No guidance is provided on when to use this tool versus alternatives such as generate_uclass or add_blueprint_function. There are no prerequisites, exclusions, or context clues indicating the intended scenario for using this generator.

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