ue_set_blueprint_default

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

The description discloses that the tool both sets a value and recompiles the Blueprint, which is a significant behavioral trait. However, no annotations are provided, and the description lacks details on side effects, failure conditions, or required permissions.

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?

A single sentence that directly states the tool's purpose without any extraneous words. Highly efficient.

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 no output schema, no annotations, and three required parameters, the description is too terse. It does not explain return values, error handling, or how to specify the value. The agent lacks sufficient context for correct invocation.

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 0%, and the description provides no additional meaning for any of the three parameters (blueprint_path, property_name, value). The schema only gives names and types, leaving the agent to guess formats and semantics.

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 verb 'Set' and the resource 'class default value on a Blueprint', and mentions the key action 'recompile'. It distinguishes from sibling tools like ue_set_actor_property which sets instance values.

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 explicit guidance on when to use this tool versus alternatives like ue_set_actor_property or ue_create_blueprint. The description implies it's for class defaults, but no when-not or alternative naming.

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