copy_static_mesh_to_dynamic_mesh

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

Annotations already declare destructive=true and idempotent=true, so the description's 'Destructive replace' and 'Idempotent-ish: re-running re-extracts the same source geometry' restate but also clarify those hints (re-running re-extracts vs. duplicates). It adds useful beyond-annotation context: the LOD clamping behavior, that the LODIndex is silently clamped, and that the result depends only on source + LOD. It does not, however, mention any required permissions or actor-not-found 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 core purpose then layers in implementation function, destructive warning, idempotency, and LOD behavior. Slightly dense at the end (LOD explanation and Returns block are lengthy), but every sentence carries information and the structure is logical.

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 3-param mutation tool with annotations covering destructive/idempotent and no output schema, the description is largely complete: it explains the operation, the destruction, idempotency semantics, and LOD clamping. It explicitly enumerates return fields inside the description (compensating for the missing output schema), which is a plus. It lacks only prerequisite/permission guidance.

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_name, source_static_mesh_path, and lod_index (including the MaxAvailable clamping). The description confirms the LODIndex clamping and the source/target relationship, adding only marginal value. Baseline 3 is appropriate when the schema does the heavy lifting.

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 (Copy) and both resources (UStaticMesh → live dynamic mesh of DynamicMeshActor), plus the exact implementation function (CopyMeshFromStaticMesh) and engine-default options. An agent can distinguish this from siblings like copy_dynamic_mesh_to_static_mesh or append_mesh_to_dynamic_mesh purely from the description.

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 implies the workflow (copy a static mesh INTO a live actor's dynamic mesh) and names the reversed sibling implicitly by describing direction. However, there is no explicit when-to-use/when-not guidance, no mention of alternatives such as append_mesh_to_dynamic_mesh or copy_dynamic_mesh_to_static_mesh, and no prerequisite for whether the actor must exist first (though 'the actor's current mesh' weakly implies it).

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