assign_skeletal_mesh_physics_asset

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the mutation profile is covered. The description adds value by disclosing the clearing semantics (null/empty removes the assignment), which the annotations alone would not convey, though it says nothing about persistence or whether a save is required afterward.

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 tight sentences: purpose and the clear variant are front-loaded, followed by a compact return-shape block. No wasted words.

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?

Although there is no formal output schema, the description enumerates the return fields (skeletal_mesh_path, physics_asset_path, assigned, cleared, physics_asset_name), and annotations carry the safety profile. Only the persistence/apply behavior after assignment is left unaddressed.

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 both parameters (skeletal_mesh_path, physics_asset_path) are fully documented in the schema and the clearing behavior is repeated there. The description adds no syntax or format meaning beyond the schema, 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?

States a specific verb (assign) and both resources (physics asset → skeletal mesh), and the parenthetical covers the clearing case. It is clearly distinguishable from physics siblings like create_physics_asset, get_physics_asset_info, or set_physics_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 notes that null/empty clears the assignment, which is a useful usage hint, but it never states when to use this tool versus alternatives (e.g. create_physics_asset or get_physics_asset_info) or any prerequisites. Usage is only implied.

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