remove_subsystem_class_bp

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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, but the description adds substantive behavioral context beyond them: the two guard checks (must be UBlueprint, generated class must derive from USubsystem), the safety consequence versus delete_asset, the idempotent-on-missing semantics, and the exact return shape. This is exactly the kind of context annotations cannot carry.

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?

Front-loaded with the purpose, followed by the safety rationale and then the return contract. Every sentence earns its place with 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 destructive single-parameter delete with no output schema, the description supplies the purpose, the guard conditions, idempotency behavior, and the return payload shape. An agent has everything needed to decide to call it and to interpret the result.

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 the single asset_path parameter is fully documented in the schema. The description reinforces the path concept ('at a package path') but adds no format or constraint detail beyond what the schema already provides, so the 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 and resource ('Destroy the Blueprint-authored USubsystem subclass at a package path') and names its counterpart ('mirror of create_subsystem_class_bp'). It also distinguishes itself from the sibling generic delete_asset, so an agent can identify it without opening the schema.

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 gives clear selection context: this is a typed-delete that only fires when the asset is a UBlueprint whose generated class derives from USubsystem, and it explicitly contrasts with the generic delete_asset that can wipe unrelated Blueprints. It lacks an explicit when-not statement (e.g., what to use for non-subsystem Blueprints), so it falls short of full 5-level routing guidance.

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