set_skeletal_mesh_lod_build_settings

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

Adds substantial context beyond the annotations: partial-update semantics ('only the fields you pass'), persistence ('save the mesh'), deferred effect ('not rebuilt here ... next build or reimport'), and an error path ('a failed save returns an error'). The annotations already declare destructive=true and idempotent=true; the description does not spell out what the destructive overwrite affects or whether it is reversible, which keeps it from a 5.

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-loaded with purpose, then behavior, then a compact Returns shape. The prose 'Returns settings_applied' and the explicit Returns line are mildly redundant, but overall it is tight and every sentence contributes.

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 appropriately documents the return shape (lod_index, settings_applied, saved), the deferred-effect behavior, and the error case. It is close to complete for an 11-param mutation tool, though it could clarify the overwrite/reversibility implied by destructiveHint.

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 coverage is 100% with detailed per-parameter descriptions (bUseMikkTSpace, DefaultBoneInfluenceLimit behavior, etc.), so the schema carries the parameter burden. The description adds only the 'only the fields you pass' partial-update note, which is a baseline-plus level of added meaning, not detailed parameter guidance.

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 and resource: change the stored build settings of one LOD of a skeletal mesh asset and save it. The clause 'The mesh is not rebuilt here' explicitly differentiates it from rebuild-style siblings like bake_skeletal_mesh_lod, and 'build settings' scopes it away from set_skeletal_mesh_lod_reduction_settings / screen_size.

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?

Gives clear context for use: settings are only persisted and 'take effect at its next build or reimport', implying this is for staging build config rather than triggering a rebuild. It does not name an explicit alternative (e.g. bake_skeletal_mesh_lod) or state exclusions, so it stops short of full when/when-not routing.

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