ue_create_blueprint

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

With no annotations, the description carries full burden. It only states 'Crea un Blueprint' without disclosing side effects, requirements (e.g., editor state), error conditions, or return behavior. Minimal insight into tool behavior beyond creation.

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?

Description is very short (two lines) and efficiently lists arguments with examples. It is well-structured with Args section. Could potentially be more concise by combining into a single sentence, but current form is clear.

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 creation tool, the description omits important context: what happens after creation (e.g., asset appears in browser), error handling (e.g., duplicate names), and dependencies (e.g., open project). Incomplete for an AI agent to use without trial and error.

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?

Given 0% schema description coverage, the description adds significant value by providing examples for package_path and name, and listing common values for parent_class. This aids understanding but lacks format constraints like required path prefix.

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 'Crea un Blueprint' clearly states the tool's function (create a blueprint). It is specific and distinguishable from siblings like ue_cpp_class_create or ue_create_material. However, it does not specify the type of blueprint (e.g., Blueprint Class) explicitly, relying on parameter examples.

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 on when to use this tool versus alternatives. The description lacks prerequisites, context (e.g., requires open project), or any indication of when this tool is appropriate. Sibling tools are not referenced or distinguished.

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