Reduce triangle count by adding a Decimate modifier with adjustable ratio and decimation type.
Add a Decimate modifier to reduce triangle count.
For LOD chains prefer create_lod, which builds named copies and leaves the source untouched.
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | ||
| ratio | No | Fraction of faces to keep, e.g. 0.5 halves them | |
| triangulate | No | ||
| decimate_type | No | COLLAPSE | |
| modifier_name | No |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must disclose behavior. It only says the modifier reduces triangle count; it does not mention whether this is destructive, whether it modifies a named object or the active object, whether the modifier is reversible, or any side effects.
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 sentences, zero filler. Purpose is front-loaded, and the sibling alternative is stated in a compact second sentence.
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 five parameters, no output schema, and no annotations, this description is too sparse. It omits how the target object is identified, how modifier naming works, and how the decimation settings behave, leaving the agent to guess from the schema.
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 only 20%, so the description must compensate, but it adds nothing about the required 'name', 'ratio', 'triangulate', 'decimate_type', or 'modifier_name' parameters. Only the schema's ratio field has a helpful description.
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: 'Add a Decimate modifier to reduce triangle count.' The second sentence differentiates it from create_lod, making the purpose and sibling distinction clear.
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?
Explicitly advises preferring create_lod for LOD chains and explains why ('builds named copies and leaves the source untouched'). This gives the agent a direct when-not-to-use signal.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.