ue_set_component_default

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

With no annotations provided, the description carries the full burden. It discloses the key behavioral trait (template vs instance) and the error scenario ("cannot be edited on instances"), plus value conversion behavior. It could go further by noting persistence to the asset or effects on existing instances, but it already provides substantial unexpected behavior context.

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 well-structured and front-loaded, with the core distinction stated first, followed by practical guidance, a concrete example, and a compact parameter list. Every sentence earns its place with no redundancy or filler.

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 tool's simplicity and the rich parameter documentation, the description is nearly complete. It lacks an explicit mention of success/error return types, but for a property setter this is a minor gap. The alternative tool reference and the example make it highly usable in context.

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%, but the description compensates fully by explaining each parameter: blueprint_path names the containing Blueprint, component_name is as seen in the editor, property_name accepts snake_case or PascalCase, and value includes detailed JSON conversion rules (vectors, rotators, colors, asset paths). This is strong added value beyond the bare schema.

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 a specific action: writing a property on a component's template inside a Blueprint, explicitly contrasted with editing an instance in the level. It distinguishes itself from related tools like ue_set_actor_property and focuses on a precise Unreal concept (EditDefaultsOnly).

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 explicit guidance on when to use this tool: for EditDefaultsOnly properties that Unreal rejects on instances, with a concrete example. It also names the alternative tool (ue_set_actor_property) for actors already in the level, making the decision clear.

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