unreal_set_actor_properties

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

With no annotations, the description carries the full burden, and it does disclose mutation, saving, the editor-open gate, and safe literal conversion. But the unconditional 'then SAVE the map' is misleading given dryRun defaults to true; the description does not state that saving only occurs when dryRun=false, which is a significant behavioral caveat.

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 dense sentences with no wasted words; the core action and side effect are front-loaded, and the mutating/refusal condition follows naturally.

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?

With 7 parameters, nested properties, no output schema, and no annotations, this description is too thin to fully support correct invocation. An agent can infer param names but not matching semantics, the maxActors safety cap, the dry-run/save relationship, or the response/error behavior.

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 must compensate. It clarifies map, actorMatch, properties, and allowWithEditorOpen, but it does not explain dryRun, maxActors, or timeoutSeconds, and it misrepresents dryRun's role as the save switch.

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 ('Set... properties') and resource ('matching actors in a map') and calls out the consequential save. It differentiates at a surface level from asset-focused siblings like unreal_set_asset_properties, though 'editor-displey-name properies' is ambiguous and the schema suggests arbitrary actor properties.

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 gives useful operational context: the operation is mutating, it saves the map, and it refuses while an editor is open unless allowWithEditorOpen. However, it does not explicitly state when this tool should be chosen over similar siblings, nor does it explain that dryRun should be used for previews; usage guidance is mostly implied.

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