bake_skeletal_mesh_lod

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and idempotentHint=false, so the safety profile is covered. The description adds little behavioral context beyond naming the underlying subsystem call; it doesn't say whether the asset is saved, what gets overwritten, or that reduction destroys existing LODs.

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 parts: a one-line purpose statement followed by the return shape. It is front-loaded and wastes no words, and the Returns list is genuinely useful given there is no output schema.

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, documenting the return fields is a real contribution, and the annotations carry the destructive/idempotency profile. However, for a destructive bake operation it omits whether the change persists or requires saving, and gives no usage context, leaving the definition only adequate.

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%, so the schema already documents all four parameters, including the <=0 semantics for new_lod_count and the defaults for the booleans. The description adds no parameter meaning beyond the schema, so the baseline 3 is appropriate.

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: it runs the skeletal-mesh reduction pipeline via RegenerateLOD, which clearly distinguishes it from getters like get_skeletal_mesh_lod_info and setters like set_skeletal_mesh_lod_reduction_settings. It does not explicitly differentiate itself from siblings such as add_skeletal_mesh_lod or remove_skeletal_mesh_lod, so it stops short of a 5.

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 gives no when-to-use guidance, no prerequisites, and no routing to alternatives. With siblings like add_skeletal_mesh_lod, set_skeletal_mesh_lod_reduction_settings, and set_skeletal_mesh_lod_settings in the same family, an agent gets no help choosing this tool over them.

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