blender_msfs_decimate_for_lod

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only says 'Decimate a mesh', which implies mutation, but it does not state whether the operation is destructive/in-place, whether the original mesh is preserved, that the ratio result is approximate rather than exact, or what the tool returns. 'Target' hints at approximation, but key behavioral details are missing.

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?

One short declarative sentence with no filler. The action and purpose are front-loaded, and every word contributes meaningful information.

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?

This is minimally viable for a simple decimate operation: the schema covers parameters well and the description clearly states the purpose. However, with no annotations and no output schema, the lack of behavioral detail—such as whether the mesh is modified in place, whether a new object is created, and how approximate the result is—leaves meaningful gaps for an agent that needs to reason about side effects.

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 documents all four parameters with descriptions and defaults, including the ratio range and boolean flags. The description's use of 'target ratio' lightly reinforces the ratio semantics but adds no new meaning beyond what the schema already provides.

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 states a specific verb ('Decimate'), a resource ('a mesh'), and an intended purpose ('for LOD creation'). It is clear on its face, though it does not explicitly distinguish itself from blender_ai_mesh_decimate or generic decimation modifiers; the LOD context and msfs prefix do most of the differentiation work.

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 phrase 'for LOD creation' gives a clear contextual signal that this tool belongs in the LOD pipeline, implying when it should be used. However, it does not explicitly state when to prefer it over alternatives like blender_ai_mesh_decimate or blender_modifier_* decimation, nor does it provide any when-not-to-use guidance.

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