Resolve an asset path and assign it to a component property on an entity, enabling asset references in O3DE components.
Assign an asset to a component property by resolving the asset path.
| Name | Required | Description | Default |
|---|---|---|---|
| entity_id | Yes | ||
| asset_path | Yes | ||
| property_path | Yes | ||
| component_type | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections.
v0.3.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of behavioral disclosure. It implies a mutating operation and mentions path resolution, but it does not explain side effects, failure modes, required asset readiness, or whether the operation is reversible.
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 a single, compact sentence with no wasted words, and it front-loads the core action. However, for a four-parameter mutation tool with no supporting details, it is under-specified rather than optimally concise.
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 tool with no annotations and four required parameters, the description does not provide enough context for correct invocation. It omits prerequisites, path resolution semantics, and any distinction from the many related component-property tools. The presence of an output schema helps, but the input semantics remain unclear.
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 adds no meaning beyond the parameter names already in the schema. Terms like 'property_path' and 'component_type' are self-explanatory at a surface level, but path formatting and how asset resolution relates to the parameters are left undocumented.
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 ('assign') and the resource ('asset to a component property'), giving an agent a high-level understanding of the operation. It does not explicitly differentiate from sibling tools like set_component_property, but the asset-focused phrasing provides reasonable distinctness.
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?
There is no guidance about when to use this tool versus alternatives such as set_component_property or instantiate_prefab, and no mention of prerequisites or conditions. The description only states what the tool does, not when it should be selected.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.