ue_pcg_set_node_property

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

With no annotations, the description carries the burden of disclosure. It adds useful context: value is JSON and /Game/ paths are loaded as assets. However, it does not disclose whether the property must already exist, whether changes are immediate, or any failure behavior or side effects of 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 very concise: a one-sentence purpose followed by a structured parameter list. Every line adds value, with no fluff or redundancy.

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 4-parameter, no-output-schema tool with no annotations, the description covers the essential context: purpose, all parameters with examples, and value special handling. It lacks details on prerequisites or error behavior, but for a simple property setter this is nearly complete.

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%, so the description compensates well. It explains each parameter in the Args list, including concrete examples for property_name ('points_per_squared_meter', 'seed') and clarifies the special JSON behavior of value with asset path loading.

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 tool's function: 'Imposta una proprietà sulle settings di un nodo PCG' (sets a property on PCG node settings). The verb 'imposta' with the resource 'proprietà... nodo PCG' is specific and distinguishes this from sibling tools like ue_bt_set_node_property.

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?

No explicit guidance on when to use this tool versus alternatives. It does not mention prerequisites, context (e.g., node must already exist), or when not to use it. The examples for property_name imply typical use but do not provide clear usage boundaries.

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