set_skeletal_mesh_lod_reduction_settings

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

Annotations already declare idempotentHint=true and destructiveHint=true, but the description adds important operational semantics: partial update and only fields present are written, which reassures the agent that omitted fields are safe. It also provides a concrete return shape despite no output schema being declared. It does not elaborate on destructive scope or permissions, so it is useful but not complete.

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?

The definition is front-loaded with purpose and then adds only high-value operational notes: partial update, enum naming, criterion/method distinction, and return shape. Every sentence earns its place, and there is no redundant restatement of the schema or tool name.

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 22-parameter authoring tool with full schema coverage, no output schema, and destructive/idempotent annotations, the description gives enough context to call it correctly: what it authors, how partial updates work, enum naming, and the return shape. It could be stronger by noting sibling alternatives or overwrite/destructive scope, but the critical invocation context is present.

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 carries most parameter meaning. The description adds value by clarifying that enums are accepted by full or short name and by explicitly distinguishing termination_criterion (SMTC_*) from reduction_method (SMOT_*), reducing a likely source of invocation error.

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 and resource: authoring a LOD's FSkeletalMeshOptimizationSettings (ReductionSettings). It also ties the resource to its consumer, bake_skeletal_mesh_lod, and the ReductionSettings scope distinguishes it from more general LOD-setting siblings. An agent can identify the exact object being configured 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?

It clearly states the usage context: this is the data bake_skeletal_mesh_lod consumes, so it is used before baking to steer reduction instead of running with defaults. It does not explicitly name alternative sibling tools or state when not to use it, so it stops short of full when/when-not/alternatives guidance.

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