set_blueprint_component_property

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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, and the description adds substantial context beyond them: the in-memory component-dropping failure and its cure (reload_asset_package with on_dirty=discard), the silent None write on object-reference properties that reports override_persisted:true, the fact that already-placed actors retain their serialized value, and the PIE/compile hazard behind force. This is exactly the extra behavioral disclosure the low annotation bar rewards.

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 purpose and the inherited-component scope before the traps, and every sentence carries information. The THREE TRAPS block and the return-value paragraph are dense and all-caps-heavy, making it longer than it needs to be to convey the same facts, but nothing is purely 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?

With no output schema, the description carries the full burden of explaining the return shape, and it does: blueprint_name, component_name, property_name, component_class, source with its four values, and override_persisted — plus the crucial caveat that neither field re-reads the value and so neither proves the write landed. Nothing an agent needs to invoke or interpret this tool is missing.

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 coverage is 100% and the schema already carries the alias note, the force/PIE warning, and the array-rewrites-everything warning, so most parameter meaning is structured. The description still adds value by clarifying that component_name may be an inherited component and that property_value uses the same importer as set_component_property, so it sits above the baseline-3 for full schema coverage.

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 precise verb+resource+scope: setting the DEFAULT of a property on a Blueprint component TEMPLATE, including components inherited from an ancestor through the InheritableComponentHandler or native inheritance. It distinguishes itself explicitly from its read-only twin get_blueprint_component_property, from apply_component_property_overrides (bulk), and from set_blueprint_component_array_element (single element), so an agent can route correctly without opening either 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?

Gives explicit when-to-use and when-to-use-something-else: bulk writes go to apply_component_property_overrides, single array elements to set_blueprint_component_array_element, reads to get_blueprint_component_property. It also states an exclusion condition (refused during PIE unless force=true) and the scope limitation that only FRESH instances observe the value.

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