create_subsystem_class_bp

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and idempotentHint=true, so the safety profile is carried by structured data; the description's 'idempotent on re-run' merely restates the annotation. It does add the already_exists return flag, which signals re-run outcomes, but omits the notable constraint that this command is refused during PIE.

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?

Two tight lines with the core action front-loaded and the return shape compactly listed. No filler, though the returns block could be trimmed given the schema already names the same fields.

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?

There is no output schema, so spelling out the returned fields (asset_name, asset_path, already_exists, etc.) is genuinely useful. Combined with 100% parameter coverage in the schema, an agent has enough to call the tool; only the PIE-refusal behavior is left to the schema rather than the description.

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%, so all four parameters are documented in the schema itself and the description adds no syntax or default detail. The mention of 'USubsystem-derivative' lightly clarifies the expected parent_class, but otherwise the schema does the work; baseline 3 applies.

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 (Create) and resource (USubsystem-derivative Blueprint asset), which an agent can distinguish from sibling creators like create_game_mode_class_bp or create_anim_blueprint. It stops short of explicitly naming the sibling it is not or the subsystem-family tools it pairs with (remove_subsystem_class_bp, list_subsystem_classes).

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 parenthetical '(idempotent on re-run)' is the only usage context offered; there is no statement of when to prefer this over other class-creation tools or what prerequisites must hold. The significant PIE restriction lives only in the schema's force parameter, not the description.

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