ue5_build_blueprint

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

With no annotations provided, the description carries the full burden and discloses important behavior: atomicity, rollback of created assets on any failure, optional compilation, and accepted node reference formats. It does not mention whether an existing asset with the same name is overwritten or whether results are saved to disk, but the disclosed transactional behavior goes well beyond a trivial statement.

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 compact despite the inherently complex spec. It front-loads the core atomic behavior, then provides a dense but parseable field listing. The bilingual tail is minimal and does not duplicate the main explanation.

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 complexity and absence of an output schema, the description does not fully stand alone: it omits return-value/result behavior, which fields are required versus optional, and some nested-field syntax details like coordinate format or property value representation. The tool is highly complex, and while the description is rich, these gaps make it not fully complete for a cold-start agent.

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 only provides an opaque 'spec' object pointing back to the description, so the description effectively documents all parameter semantics. It enumerates every spec field with nested structure, lists the event/function node formats, and explains how node references can be specified (32-hex GUIDs recommended or titles).

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 states a specific verb ('Create a Blueprint from scratch') and a precise resource scope: asset, variables, components, interfaces, events, function nodes, connections, and optional compile. The phrase 'one atomic call' and 'from scratch' clearly distinguishes this from siblings like ue5_compile_blueprint or ue5_connect_pins.

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 makes it clear this tool is for full blueprint creation in a single atomic operation, which implies it is the right choice when building a new asset rather than modifying or compiling an existing one. It does not explicitly name alternatives or state when not to use it, but the 'from scratch' framing gives strong contextual guidance.

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