append_mesh_to_dynamic_mesh

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

Annotations already disclose the mutation profile (readOnly=false, idempotent=false, destructive=false), and the description is consistent with them. It adds a return contract (triangles_added, vertex_count_after) that conveys the observable effect and confirms it modifies the live mesh, but it omits preconditions such as whether the source actor is consumed or preserved and whether the mesh must be non-empty. With annotations covering safety, this is adequate context, not rich.

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 sentences, zero filler: the action and its target lead, and the return shape follows. The return list earns its place because there is no output schema. Nothing is restated from the name or title.

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 mutating mesh tool with no output schema, the description compensates by spelling out the return payload and validating that the append succeeded (appended: true). Parameters are fully covered by the schema. It falls short only on failure behavior and source-mesh disposition, which an agent might still need.

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%, with actor_name, source_actor_name and append_transform each documented in the schema. The description adds no syntax or behavior beyond what the schema provides (e.g. append_transform's identity default is already stated there), so the baseline of 3 applies.

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 names a specific verb (Merge/Append) and both resources precisely: a source UDynamicMesh merged into the live dynamic mesh of a target DynamicMeshActor. This distinguishes it from the closest sibling, append_mesh_primitive, because it explicitly appends another dynamic mesh rather than a primitive, so an agent can choose correctly without opening the schema.

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 merge semantics imply when to use it (combining two existing dynamic mesh actors), but the description gives no explicit when-to-use/when-not guidance and names no alternative such as append_mesh_primitive or copy_static_mesh_to_dynamic_mesh. Usage must be inferred from the purpose statement.

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