set_component_property

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

No annotations are present, so the description carries the obligation to disclose mutation behavior and constraints. It only says 'Set any property' with no mention of side effects (e.g., requiring compile or save), limits on which properties are actually settable, or failure behaviors if the blueprint or component does not exist. The value-type hint is useful, but operational consequences are absent.

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 and well-organized: a one-sentence purpose, a concise args list, a KB reference, and a single example. Every element earns its place; the KB reference is short and optional. It is not bloated and is front-loaded with the key action.

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 complexity (4 parameters, no annotations, output schema exists but its contents are unseen), the description provides essential input details and an example sufficient for a basic call. However, it omits error handling specifics, whether the change persists to disk, or if a compile/save is required. It also doesn't clarify whether 'any property' actually includes all properties or only those marked BlueprintReadWrite. Thus, while adequate for straightforward usage, it leaves gaps for edge cases.

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 0% (all parameters are just typed as string), so the description must add meaning. It does: each parameter is briefly defined, including an example of C++ property names and valid property_value types (bool, int, float, string, [x,y,z] array). The example usage with actual path and values reinforces semantics. Some ambiguity remains (e.g., blueprint_name format, how bool is represented), but the description meaningfully compensates for the minimal 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 opens with 'Set any property on a Blueprint component,' which names a specific verb (set), a specific resource (Blueprint component), and the general scope (any property). The parameter list and example further clarify the resource type (component) and distinguish it from sibling tools like set_actor_property or set_blueprint_property. This is precise and unambiguous.

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 implies usage: when you need to set a property on a Blueprint component, use this tool. It does not explicitly mention alternatives or state when not to use it, nor does it reference sibling tools like set_actor_property. The context is clear enough but the guidance is implied rather than stated.

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