set_pcg_component_properties

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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the safety profile is partly covered. The description goes further by disclosing the reflection mechanism, the partial-success model (a 'failed' list with per-property errors), and the value readback into 'applied' — context the annotations do not provide. It does not, however, clarify what is destroyed or the failure conditions for reflection.

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?

Two tightly written sentences plus a return-shape block, all front-loaded with the core action first. No filler, and the return structure is valuable given there is no output schema.

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 mutation tool with no output schema, the description supplies the return shape, which compensates well. It is nearly complete, though it omits reflection failure modes and whether the write persists beyond the editor session.

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 both parameters are documented in the schema, so the baseline is 3. The description earns above-baseline credit by giving concrete example property keys for the free-form 'properties' object, which is genuinely useful guidance for an additionalProperties object.

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 specific verb ('Sets properties'), a specific resource (an actor's UPCGComponent), and enumerates real property names (Seed, bActivated, bIsComponentPartitioned, GenerationTrigger). This clearly distinguishes it from siblings like set_pcg_graph_parameter and set_pcg_node_properties, which operate on different PCG objects.

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 explains the mechanism ('by reflection') but gives no when-to-use, when-not-to-use, or alternative routing. An agent cannot tell from the text whether this is preferable to add_pcg_graph_parameter or set_pcg_node_properties for a given goal.

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