decimate

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

The description states 'Applies modifier immediately', indicating that the decimation is applied destructively. However, with no annotations, it fails to mention other behavioral traits such as whether the operation is reversible or what happens to the original mesh data. Some transparency is present but incomplete.

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 description is extremely concise at three short sentences with no wasted words. It front-loads the main action and provides essential detail about the ratio parameter. Every sentence earns its place.

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?

Given the lack of output schema and 0% schema coverage, the description is incomplete. It does not explain the 'name' parameter, nor does it describe the return value or side effects beyond applying the modifier. With many sibling tools, more context about the tool's scope and behavior is needed.

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?

The description explains the 'ratio' parameter with a clear example ('Ratio 0.5 = reduce to 50% of original faces') and its effect. However, the 'name' parameter is not explained, leaving the user to infer it likely refers to the object name. With 0% schema coverage, the description should cover both parameters.

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 clearly states 'Reduce mesh polygon count', which is a specific verb and resource. However, it does not differentiate from the sibling tool 'vrc_decimate' which likely serves a similar purpose for VRChat. The purpose is clear but lacks distinction.

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 provides no guidance on when to use this tool versus alternatives such as 'vrc_decimate' or other modifier-related tools. There is no mention of prerequisites or conditions for use.

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