set_actor_replicate_movement

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

Adds substantial context beyond annotations: clarifies it's not marked dirty and nothing is saved, and that only the placed instance (not class defaults) is affected. Annotations already flag destructiveHint=true; the description explains the actual blast radius, which is the valuable addition. Doesn't discuss undo/transaction behavior.

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?

Front-loads the tool's action, then scoping caveat, then read-back hint, ending with the return shape. Slightly dense in one paragraph but each clause earns its place.

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 no output schema, the description helpfully states the return shape ({actor_label, replicate_movement}). Covers scope, non-persistence, and read-back. Missing only transaction/undo semantics, which is minor for this tool.

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 100%, so the schema already documents actor_label and replicate_movement. Baseline 3 applies; the description adds only that replicate_movement echoes the request rather than extending parameter meaning.

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+resource: 'Set bReplicateMovement on an editor-world actor found by label' and cites the underlying API (AActor::SetReplicateMovement). This is precise and distinguishable from siblings like set_actor_replicates.

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?

Explains the scope constraint clearly ('only that placed instance changes, not its class defaults') and points to a read-back path via get_actor_replication_info. No explicit when-not guidance, but the constraint implies the boundary well.

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