set_blueprint_property

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

With no annotations, the description carries the full burden of behavioral disclosure. It says the property is set on the CDO, but does not explain whether existing placed instances are affected, whether the asset needs recompiling, what happens on invalid property names, or any side effects of this mutation.

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 tight and well-structured: one-line purpose, Args list, KB pointer, and example. Every sentence contributes, and the important action is front-loaded.

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 simple three-string-parameter setter, the description is largely sufficient and the output schema covers return shape. However, the lack of annotation coverage means it should disclose more about mutation scope, such as whether existing instances remain unchanged or whether compilation is required afterward.

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% and the schema only provides parameter names, so the description must add meaning. The Args section gives useful definitions and concrete examples for property_name values, plus a full example call with a realistic asset path and value.

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 it sets a property on the Blueprint class default object (CDO), which is a specific verb-resource pair. Mentioning CDO distinguishes this from instance-level setters like set_actor_property, though it does not explicitly name that sibling.

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 CDO wording implies this tool is for changing Blueprint class defaults rather than actor instances or component properties. However, there is no explicit when-to-use or when-not-to-use guidance, and no alternative tools are named.

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